Device, and method of decoding video data

ABSTRACT

A device may be configured to decoding capability information according to one or more of the techniques described herein.

TECHNICAL FIELD

This disclosure relates to video coding and more particularly to techniques for signaling decoding capability information for coded video.

BACKGROUND

Digital video capabilities can be incorporated into a wide range of devices, including digital televisions, laptop or desktop computers, tablet computers, digital recording devices, digital media players, video gaming devices, cellular telephones, including so-called smartphones, medical imaging devices, and the like. Digital video may be coded according to a video coding standard. Video coding standards define the format of a compliant bitstream encapsulating coded video data. A compliant bitstream is a data structure that may be received and decoded by a video decoding device to generate reconstructed video data. Video coding standards may incorporate video compression techniques. Examples of video coding standards include ISO/IEC MPEG-4 Visual and ITU-T H.264 (also known as ISO/IEC MPEG-4 AVC) and High-Efficiency Video Coding (HEVC). HEVC is described in High Efficiency Video Coding (HEVC), Rec. ITU-T H.265, December 2016, which is incorporated by reference, and referred to herein as ITU-T H.265. Extensions and improvements for ITU-T H.265 are currently being considered for the development of next generation video coding standards. For example, the ITU-T Video Coding Experts Group (VCEG) and ISO/IEC (Moving Picture Experts Group (MPEG) (collectively referred to as the Joint Video Exploration Team (JVET)) are working to standardized video coding technology with a compression capability that significantly exceeds that of the current HEVC standard. The Joint Exploration Model 7 (JEM 7), Algorithm Description of Joint Exploration Test Model 7 (JEM 7), ISO/IEC JTC1/SC29/WG11 Document: JVET-G1001, July 2017, Torino, IT, which is incorporated by reference herein, describes the coding features that were under coordinated test model study by the JVET as potentially enhancing video coding technology beyond the capabilities of ITU-T H.265. It should be noted that the coding features of JEM 7 are implemented in JEM reference software. As used herein, the term JEM may collectively refer to algorithms included in JEM 7 and implementations of JEM reference software. Further, in response to a “Joint Call for Proposals on Video Compression with Capabilities beyond HEVC,” jointly issued by VCEG and MPEG, multiple descriptions of video coding tools were proposed by various groups at the 10^(th) Meeting of ISO/IEC JTC1/SC29/WG11 16-20 April 2018, San Diego, Calif. From the multiple descriptions of video coding tools, a resulting initial draft text of a video coding specification is described in “Versatile Video Coding (Draft 1),” 10^(th) Meeting of ISO/IEC JTC1/SC29/WG11 16-20 April 2018, San Diego, Calif, document JVET-J1001-v2, which is incorporated by reference herein, and referred to as JVET-J1001. The current development of a next generation video coding standard by the VCEG and MPEG is referred to as the Versatile Video Coding (VVC) project. “Versatile Video Coding (Draft 8),” 17th Meeting of ISO/IEC JTC1/SC29/WG11 7-17 January 2020, Brussel, BE, document JVET-Q2001-vE, which is incorporated by reference herein, and referred to as JVET-Q2001, represents the current iteration of the draft text of a video coding specification corresponding to the VVC project.

Video compression techniques enable data requirements for storing and transmitting video data to be reduced. Video compression techniques may reduce data requirements by exploiting the inherent redundancies in a video sequence. Video compression techniques may sub-divide a video sequence into successively smaller portions (i.e., groups of pictures within a video sequence, a picture within a group of pictures, regions within a picture, sub-regions within regions, etc.). Intra prediction coding techniques (e.g., spatial prediction techniques within a picture) and inter prediction techniques (i.e., inter-picture techniques (temporal)) may be used to generate difference values between a unit of video data to be coded and a reference unit of video data. The difference values may be referred to as residual data. Residual data may be coded as quantized transform coefficients. Syntax elements may relate residual data and a reference coding unit (e.g., intra-prediction mode indices, and motion information). Residual data and syntax elements may be entropy coded. Entropy encoded residual data and syntax elements may be included in data structures forming a compliant bitstream.

SUMMARY OF INVENTION

A method of decoding video data, the method comprising:

receiving decoding capability information; parsing a zero four bits syntax element being equal to 0 in the decoding capability information, wherein the zero four bits syntax element is an unsigned integer using 4 bits; and

parsing a syntax element in the decoding capability information, wherein the syntax element plus 1 specifies a number of profile tier level syntax structures in the decoding capability information,

wherein the syntax element is parsed immediately following the zero four bits syntax element.

A device comprising one or more processors configured to:

receive decoding capability information;

parse a zero four bits syntax element being equal to 0 in the decoding capability information, wherein the zero four bits syntax element is an unsigned integer using 4 bits; and

parse a syntax element in the decoding capability information, wherein the syntax element plus 1 specifies a number of profile tier level syntax structures in the decoding capability information,

wherein the syntax element is parsed immediately following the zero four bits syntax element.

A method of encoding video data, the method comprising:

signaling capability information,

wherein

the capability information includes:

(i) a zero four bits syntax element being equal to 0, wherein the zero four bits syntax element is an unsigned integer using 4 bits and

(ii) a syntax element, wherein the syntax element plus 1 specifies a number of profile tier level syntax structures in the decoding capability information, and

the syntax element is parsed immediately following the zero four bits syntax

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example of a system that may be configured to encode and decode video data according to one or more techniques of this disclosure.

FIG. 2 is a conceptual diagram illustrating coded video data and corresponding data structures according to one or more techniques of this disclosure.

FIG. 3 is a conceptual diagram illustrating a data structure encapsulating coded video data and corresponding metadata according to one or more techniques of this disclosure.

FIG. 4 is a conceptual drawing illustrating an example of components that may be included in an implementation of a system that may be configured to encode and decode video data according to one or more techniques of this disclosure.

FIG. 5 is a block diagram illustrating an example of a video encoder that may be configured to encode video data according to one or more techniques of this disclosure.

FIG. 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data according to one or more techniques of this disclosure.

DETAILED DESCRIPTION

In general, this disclosure describes various techniques for coding video data. In particular, this disclosure describes techniques for signaling decoding capability information for coded video data. It should be noted that although techniques of this disclosure are described with respect to ITU-T H.264, ITU-T H.265, JEM, and JVET-Q2001, the techniques of this disclosure are generally applicable to video coding. For example, the coding techniques described herein may be incorporated into video coding systems, (including video coding systems based on future video coding standards) including video block structures, intra prediction techniques, inter prediction techniques, transform techniques, filtering techniques, and/or entropy coding techniques other than those included in ITU-T H.265, JEM, and JVET-Q2001. Thus, reference to ITU-T H.264, ITU-T H.265, JEM, and/or JVET-Q2001 is for descriptive purposes and should not be construed to limit the scope of the techniques described herein. Further, it should be noted that incorporation by reference of documents herein is for descriptive purposes and should not be construed to limit or create ambiguity with respect to terms used herein. For example, in the case where an incorporated reference provides a different definition of a term than another incorporated reference and/or as the term is used herein, the term should be interpreted in a manner that broadly includes each respective definition and/or in a manner that includes each of the particular definitions in the alternative.

In one example, a method of signaling parameters for video data comprises signaling a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits, and conditionally signaling a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

In one example, a device comprises one or more processors configured to signal a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits, and conditionally signal a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

In one example, a non-transitory computer-readable storage medium comprises instructions stored thereon that, when executed, cause one or more processors of a device to signal a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits, and conditionally signal a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

In one example, an apparatus comprises means for signaling a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits, and means for conditionally signaling a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

In one example, a method of decoding video data comprises parsing a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits and conditionally parsing a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

In one example, a device comprises one or more processors configured to parse a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits and conditionally parse a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

In one example, a non-transitory computer-readable storage medium comprises instructions stored thereon that, when executed, cause one or more processors of a device to parse a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits and conditionally parse a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

In one example, an apparatus comprises means for parsing a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits and means for conditionally parsing a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.

Video content includes video sequences comprised of a series of frames (or pictures). A series of frames may also be referred to as a group of pictures (GOP). Each video frame or picture may divided into one or more regions. Regions may be defined according to a base unit (e.g., a video block) and sets of rules defining a region. For example, a rule defining a region may be that a region must be an integer number of video blocks arranged in a rectangle. Further, video blocks in a region may be ordered according to a scan pattern (e.g., a raster scan). As used herein, the term video block may generally refer to an area of a picture or may more specifically refer to the largest array of sample values that may be predictively coded, sub-divisions thereof, and/or corresponding structures. Further, the term current video block may refer to an area of a picture being encoded or decoded. A video block may be defined as an array of sample values. It should be noted that in some cases pixel values may be described as including sample values for respective components of video data, which may also be referred to as color components, (e.g., luma (Y) and chroma (Cb and Cr) components or red, green, and blue components). It should be noted that in some cases, the terms pixel value and sample value are used interchangeably. Further, in some cases, a pixel or sample may be referred to as a pel. A video sampling format, which may also be referred to as a chroma format, may define the number of chroma samples included in a video block with respect to the number of luma samples included in a video block. For example, for the 4:2:0 sampling format, the sampling rate for the luma component is twice that of the chroma components for both the horizontal and vertical directions.

A video encoder may perform predictive encoding on video blocks and sub-divisions thereof. Video blocks and sub-divisions thereof may be referred to as nodes. ITU-T H.264 specifies a macroblock including 16×16 luma samples. That is, in ITU-T H.264, a picture is segmented into macroblocks. ITU-T H.265 specifies an analogous Coding Tree Unit (CTU) structure (which may be referred to as a largest coding unit (LCU)). In ITU-T H.265, pictures are segmented into CTUs. In ITU-T H.265, for a picture, a CTU size may be set as including 16×16, 32×32, or 64×64 luma samples. In ITU-T H.265, a CTU is composed of respective Coding Tree Blocks (CTB) for each component of video data (e.g., luma (Y) and chroma (Cb and Cr). It should be noted that video having one luma component and the two corresponding chroma components may be described as having two channels, i.e., a luma channel and a chroma channel. Further, in ITU-T H.265, a CTU may be partitioned according to a quadtree (QT) partitioning structure, which results in the CTBs of the CTU being partitioned into Coding Blocks (CB). That is, in ITU-T H.265, a CTU may be partitioned into quadtree leaf nodes. According to ITU-T H.265, one luma CB together with two corresponding chroma CBs and associated syntax elements are referred to as a coding unit (CU). In ITU-T H.265, a minimum allowed size of a CB may be signaled. In ITU-T H.265, the smallest minimum allowed size of a luma CB is 8×8 luma samples. In ITU-T H.265, the decision to code a picture area using intra prediction or inter prediction is made at the CU level.

In ITU-T H.265, a CU is associated with a prediction unit structure having its root at the CU. In ITU-T H.265, prediction unit structures allow luma and chroma CBs to be split for purposes of generating corresponding reference samples. That is, in ITU-T H.265, luma and chroma CBs may be split into respective luma and chroma prediction blocks (PBs), where a PB includes a block of sample values for which the same prediction is applied. In ITU-T H.265, a CB may be partitioned into 1, 2, or 4 PBs. ITU-T H.265 supports PB sizes from 64×64 samples down to 4×4 samples. In ITU-T H.265, square PBs are supported for intra prediction, where a CB may form the PB or the CB may be split into four square PBs. In ITU-T H.265, in addition to the square PBs, rectangular PBs are supported for inter prediction, where a CB may be halved vertically or horizontally to form PBs. Further, it should be noted that in ITU-T H.265, for inter prediction, four asymmetric PB partitions are supported, where the CB is partitioned into two PBs at one quarter of the height (at the top or the bottom) or width (at the left or the right) of the CB. Intra prediction data (e.g., intra prediction mode syntax elements) or inter prediction data (e.g., motion data syntax elements) corresponding to a PB is used to produce reference and/or predicted sample values for the PB.

JEM specifies a CTU having a maximum size of 256×256 luma samples. JEM specifies a quadtree plus binary tree (QTBT) block structure. In JEM, the QTBT structure enables quadtree leaf nodes to be further partitioned by a binary tree (BT) structure. That is, in JEM, the binary tree structure enables quadtree leaf nodes to be recursively divided vertically or horizontally. In JVET-Q2001, CTUs are partitioned according a quadtree plus multi-type tree (QTMT or QT+MTT) structure. The QTMT in JVET-Q2001 is similar to the QTBT in JEM. However, in JVET-Q2001, in addition to indicating binary splits, the multi-type tree may indicate so-called ternary (or triple tree (TT)) splits. A ternary split divides a block vertically or horizontally into three blocks. In the case of a vertical TT split, a block is divided at one quarter of its width from the left edge and at one quarter its width from the right edge and in the case of a horizontal TT split a block is at one quarter of its height from the top edge and at one quarter of its height from the bottom edge.

As described above, each video frame or picture may be divided into one or more regions. For example, according to ITU-T H.265, each video frame or picture may be partitioned to include one or more slices and further partitioned to include one or more tiles, where each slice includes a sequence of CTUs (e.g., in raster scan order) and where a tile is a sequence of CTUs corresponding to a rectangular area of a picture. It should be noted that a slice, in ITU-T H.265, is a sequence of one or more slice segments starting with an independent slice segment and containing all subsequent dependent slice segments (if any) that precede the next independent slice segment (if any). A slice segment, like a slice, is a sequence of CTUs. Thus, in some cases, the terms slice and slice segment may be used interchangeably to indicate a sequence of CTUs arranged in a raster scan order. Further, it should be noted that in ITU-T H.265, a tile may consist of CTUs contained in more than one slice and a slice may consist of CTUs contained in more than one tile. However, ITU-T H.265 provides that one or both of the following conditions shall be fulfilled: (1) All CTUs in a slice belong to the same tile; and (2) All CTUs in a tile belong to the same slice.

With respect to JVET-Q2001, slices are required to consist of an integer number of complete tiles or an integer number of consecutive complete CTU rows within a tile, instead of only being required to consist of an integer number of CTUs. It should be noted that in JVET-Q2001, the slice design does not include slice segments (i.e., no independent/dependent slice segments). Thus, in JVET-Q2001, a picture may include a single tile, where the single tile is contained within a single slice or a picture may include multiple tiles where the multiple tiles (or CTU rows thereof) may be contained within one or more slices. In JVET-Q2001, the partitioning of a picture into tiles is specified by specifying respective heights for tile rows and respective widths for tile columns. Thus, in JVET-Q2001 a tile is a rectangular region of CTUs within a particular tile row and a particular tile column position. Further, it should be noted that JVET-Q2001 provides where a picture may be partitioned into subpictures, where a subpicture is a rectangular region of a CTUs within a picture. The top-left CTU of a subpicture may be located at any CTU position within a picture with subpictures being constrained to include one or more slices Thus, unlike a tile, a subpicture is not necessarily limited to a particular row and column position. It should be noted that subpictures may be useful for encapsulating regions of interest within a picture and a sub-bitstream extraction process may be used to only decode and display a particular region of interest. That is, as described in further detail below, a bitstream of coded video data includes a sequence of network abstraction layer (NAL) units, where a NAL unit encapsulates coded video data, (i.e., video data corresponding to a slice of picture) or a NAL unit encapsulates metadata used for decoding video data (e.g., a parameter set) and a sub-bitstream extraction process forms a new bitstream by removing one or more NAL units from a bitstream.

FIG. 2 is a conceptual diagram illustrating an example of a picture within a group of pictures partitioned according to tiles, slices, and subpictures. It should be noted that the techniques described herein may be applicable to tiles, slices, subpictures, sub-divisions thereof and/or equivalent structures thereto. That is, the techniques described herein may be generally applicable regardless of how a picture is partitioned into regions. For example, in some cases, the techniques described herein may be applicable in cases where a tile may be partitioned into so-called bricks, where a brick is a rectangular region of CTU rows within a particular tile. Further, for example, in some cases, the techniques described herein may be applicable in cases where one or more tiles may be included in so-called tile groups, where a tile group includes an integer number of adjacent tiles. In the example illustrated in FIG. 2 , Pic₃ is illustrated as including 16 tiles (i.e., Tile₀ to Tile₁₅) and three slices (i.e., Slice₀ to Slice₂). In the example illustrated in FIG. 2 , Slice₀ includes four tiles (i.e., Tile₀ to Tile₃), Slice₁ includes eight tiles (i.e., Tile₄ to Tile₁₁), and Slice₂ includes four tiles (i.e., Tile₁₂ to Tile₁₅). Further, as illustrated in the example of FIG. 2 , Pic₃ is illustrated as including two subpictures (i.e., Subpicture₀ and Subpicture₁), where Subpicture₀ includes Slice₀ and Slice₁ and where Subpicture₁ includes Slice₂. As described above, subpictures may be useful for encapsulating regions of interest within a picture and a sub-bitstream extraction process may be used in order to selectively decode (and display) a region interest. For example, referring to FIG. 2 , Subpicture₀ may corresponding to an action portion of a sporting event presentation (e.g., a view of the field) and Subpicture₁ may corresponding to a scrolling banner displayed during the sporting event presentation. By using organizing a picture into subpictures in this manner, a viewer may be able to disable the display of the scrolling banner. That is, through a sub-bitstream extraction process Slice₂NAL unit may be removed from a bitstream (and thus not decoded and/or displayed) and Slice₀ NAL unit and Slice₁ NAL unit may be decoded and displayed. The encapsulation of slices of a picture into respective NAL unit data structures and sub-bitstream extraction are described in further detail below.

For intra prediction coding, an intra prediction mode may specify the location of reference samples within a picture. In ITU-T H.265, defined possible intra prediction modes include a planar (i.e., surface fitting) prediction mode, a DC (i.e., flat overall averaging) prediction mode, and 33 angular prediction modes (predMode: 2-34). In JEM, defined possible intra-prediction modes include a planar prediction mode, a DC prediction mode, and 65 angular prediction modes. It should be noted that planar and DC prediction modes may be referred to as non-directional prediction modes and that angular prediction modes may be referred to as directional prediction modes. It should be noted that the techniques described herein may be generally applicable regardless of the number of defined possible prediction modes.

For inter prediction coding, a reference picture is determined and a motion vector (MV) identifies samples in the reference picture that are used to generate a prediction for a current video block. For example, a current video block may be predicted using reference sample values located in one or more previously coded picture(s) and a motion vector is used to indicate the location of the reference block relative to the current video block. A motion vector may describe, for example, a horizontal displacement component of the motion vector (i.e., MV_(x)), a vertical displacement component of the motion vector (i.e., MV_(y)), and a resolution for the motion vector (e.g., one-quarter pixel precision, one-half pixel precision, one-pixel precision, two-pixel precision, four-pixel precision). Previously decoded pictures, which may include pictures output before or after a current picture, may be organized into one or more to reference pictures lists and identified using a reference picture index value. Further, in inter prediction coding, uni-prediction refers to generating a prediction using sample values from a single reference picture and bi-prediction refers to generating a prediction using respective sample values from two reference pictures. That is, in uni-prediction, a single reference picture and corresponding motion vector are used to generate a prediction for a current video block and in bi-prediction, a first reference picture and corresponding first motion vector and a second reference picture and corresponding second motion vector are used to generate a prediction for a current video block. In bi-prediction, respective sample values are combined (e.g., added, rounded, and clipped, or averaged according to weights) to generate a prediction. Pictures and regions thereof may be classified based on which types of prediction modes may be utilized for encoding video blocks thereof. That is, for regions having a B type (e.g., a B slice), bi-prediction, uni-prediction, and intra prediction modes may be utilized, for regions having a P type (e.g., a P slice), uni-prediction, and intra prediction modes may be utilized, and for regions having an I type (e.g., an I slice), only intra prediction modes may be utilized. As described above, reference pictures are identified through reference indices. For example, for a P slice, there may be a single reference picture list, RefPicList0 and for a B slice, there may be a second independent reference picture list, RefPicList1, in addition to RefPicList0. It should be noted that for uni-prediction in a B slice, one of RefPicList0 or RefPicList1 may be used to generate a prediction. Further, it should be noted that during the decoding process, at the onset of decoding a picture, reference picture list(s) are generated from previously decoded pictures stored in a decoded picture buffer (DPB).

Further, a coding standard may support various modes of motion vector prediction. Motion vector prediction enables the value of a motion vector for a current video block to be derived based on another motion vector. For example, a set of candidate blocks having associated motion information may be derived from spatial neighboring blocks and temporal neighboring blocks to the current video block. Further, generated (or default) motion information may be used for motion vector prediction. Examples of motion vector prediction include advanced motion vector prediction (AMVP), temporal motion vector prediction (TMVP), so-called “merge” mode, and “skip” and “direct” motion inference. Further, other examples of motion vector prediction include advanced temporal motion vector prediction (ATMVP) and Spatial-temporal motion vector prediction (STMVP). For motion vector prediction, both a video encoder and video decoder perform the same process to derive a set of candidates. Thus, for a current video block, the same set of candidates is generated during encoding and decoding.

As described above, for inter prediction coding, reference samples in a previously coded picture are used for coding video blocks in a current picture. Previously coded pictures which are available for use as reference when coding a current picture are referred as reference pictures. It should be noted that the decoding order does not necessary correspond with the picture output order, i.e., the temporal order of pictures in a video sequence. In ITU-T H.265, when a picture is decoded it is stored to a decoded picture buffer (DPB) (which may be referred to as frame buffer, a reference buffer, a reference picture buffer, or the like). In ITU-T H.265, pictures stored to the DPB are removed from the DPB when they been output and are no longer needed for coding subsequent pictures. In ITU-T H.265, a determination of whether pictures should be removed from the DPB is invoked once per picture, after decoding a slice header, i.e., at the onset of decoding a picture. For example, referring to FIG. 2 , Pic₂ is illustrated as referencing Pic₁. Similarly, Pic₃ is illustrated as referencing Pic₀. With respect to FIG. 2 , assuming the picture number corresponds to the decoding order, the DPB would be populated as follows: after decoding Pic₀, the DPB would include {Pic₀}; at the onset of decoding Pic₁, the DPB would include {Pic₀}; after decoding Pic₁, the DPB would include {Pic₀, Pic₁}; at the onset of decoding Pic₂, the DPB would include {Pic₀, Pic₁}. Pic₂ would then be decoded with reference to Pic₁ and after decoding Pic₂, the DPB would include {Pic₀, Pic₁, Pic₂}. At the onset of decoding Pic₃, pictures Pic₀ and Pic₁ would be marked for removal from the DPB, as they are not needed for decoding Pic₃ (or any subsequent pictures, not shown) and assuming Pic₁ and Pic₂ have been output, the DPB would be updated to include {Pic₀}. Pic₃ would then be decoded by referencing Pic₀. The process of marking pictures for removal from a DPB may be referred to as reference picture set (RPS) management.

As described above, intra prediction data or inter prediction data is used to produce reference sample values for a block of sample values. The difference between sample values included in a current PB, or another type of picture area structure, and associated reference samples (e.g., those generated using a prediction) may be referred to as residual data. Residual data may include respective arrays of difference values corresponding to each component of video data. Residual data may be in the pixel domain. A transform, such as, a discrete cosine transform (DCT), a discrete sine transform (DST), an integer transform, a wavelet transform, or a conceptually similar transform, may be applied to an array of difference values to generate transform coefficients. It should be noted that in ITU-T H.265 and WET-Q2001, a CU is associated with a transform tree structure having its root at the CU level. The transform tree is partitioned into one or more transform units (TUs). That is, an array of difference values may be partitioned for purposes of generating transform coefficients (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values). For each component of video data, such sub-divisions of difference values may be referred to as Transform Blocks (TBs). It should be noted that in some cases, a core transform and subsequent secondary transforms may be applied (in the video encoder) to generate transform coefficients. For a video decoder, the order of transforms is reversed.

A quantization process may be performed on transform coefficients or residual sample values directly (e.g., in the case, of palette coding quantization). Quantization approximates transform coefficients by amplitudes restricted to a set of specified values. Quantization essentially scales transform coefficients in order to vary the amount of data required to represent a group of transform coefficients. Quantization may include division of transform coefficients (or values resulting from the addition of an offset value to transform coefficients) by a quantization scaling factor and any associated rounding functions (e.g., rounding to the nearest integer). Quantized transform coefficients may be referred to as coefficient level values. Inverse quantization (or “dequantization”) may include multiplication of coefficient level values by the quantization scaling factor, and any reciprocal rounding or offset addition operations. It should be noted that as used herein the term quantization process in some instances may refer to division by a scaling factor to generate level values and multiplication by a scaling factor to recover transform coefficients in some instances. That is, a quantization process may refer to quantization in some cases and inverse quantization in some cases. Further, it should be noted that although in some of the examples below quantization processes are described with respect to arithmetic operations associated with decimal notation, such descriptions are for illustrative purposes and should not be construed as limiting. For example, the techniques described herein may be implemented in a device using binary operations and the like. For example, multiplication and division operations described herein may be implemented using bit shifting operations and the like.

Quantized transform coefficients and syntax elements (e.g., syntax elements indicating a coding structure for a video block) may be entropy coded according to an entropy coding technique. An entropy coding process includes coding values of syntax elements using lossless data compression algorithms. Examples of entropy coding techniques include content adaptive variable length coding (CAVLC), context adaptive binary arithmetic coding (CABAC), probability interval partitioning entropy coding (PIPE), and the like. Entropy encoded quantized transform coefficients and corresponding entropy encoded syntax elements may form a compliant bitstream that can be used to reproduce video data at a video decoder. An entropy coding process, for example, CABAC, may include performing a binarization on syntax elements. Binarization refers to the process of converting a value of a syntax element into a series of one or more bits. These bits may be referred to as “bins.” Binarization may include one or a combination of the following coding techniques: fixed length coding, unary coding, truncated unary coding, truncated Rice coding, Golomb coding, k-th order exponential Golomb coding, and Golomb-Rice coding. For example, binarization may include representing the integer value of 5 for a syntax element as 00000101 using an 8-bit fixed length binarization technique or representing the integer value of 5 as 11110 using a unary coding binarization technique. As used herein each of the terms fixed length coding, unary coding, truncated unary coding, truncated Rice coding, Golomb coding, k-th order exponential Golomb coding, and Golomb-Rice coding may refer to general implementations of these techniques and/or more specific implementations of these coding techniques. For example, a Golomb-Rice coding implementation may be specifically defined according to a video coding standard. In the example of CABAC, for a particular bin, a context provides a most probable state (MPS) value for the bin (i.e., an MPS for a bin is one of 0 or 1) and a probability value of the bin being the MPS or the least probably state (LPS). For example, a context may indicate, that the MPS of a bin is 0 and the probability of the bin being 1 is 0.3. It should be noted that a context may be determined based on values of previously coded bins including bins in the current syntax element and previously coded syntax elements. For example, values of syntax elements associated with neighboring video blocks may be used to determine a context for a current bin.

With respect to the equations used herein, the following arithmetic operators may be used:

-   + Addition -   − Subtraction -   * Multiplication, including matrix multiplication -   x^(y) Exponentiation. Specifies x to the power of y. In other     contexts, such notation is used for superscripting not intended for     interpretation as exponentiation. -   / Integer division with truncation of the result toward zero. For     example, 7/4 and −7/−4 are truncated to 1 and −7/4 and 7/−4 are     truncated to −1. -   ÷ Used to denote division in mathematical equations where no     truncation or rounding is intended.

$\frac{x}{y}$

Used to denote division in mathematical equations where no truncation or rounding is intended.

Further, the following mathematical functions may be used:

Log2(x) the base-2 logarithm of x;

${{Min}\left( {x,y} \right)} = \left\{ {\begin{matrix} x & ; & {x<=y} \\ y & ; & {x > y} \end{matrix};} \right.$ ${{Max}\left( {x,y} \right)} = \left\{ \begin{matrix} x & ; & {x>=y} \\ y & ; & {x < y} \end{matrix} \right.$

Ceil(x) the smallest integer greater than or equal to x.

With respect to the example syntax used herein, the following definitions of logical operators may be applied:

x && y Boolean logical “and” of x and y

x||y Boolean logical “or” of x and y

! Boolean logical “not”

x ? y:z If x is TRUE or not equal to 0, evaluates to the value of y; otherwise, evaluates to the value of z.

Further, the following relational operators may be applied:

> Greater than

>= Greater than or equal to

< Less than

<= Less than or equal to

== Equal to

!= Not equal to

Further, it should be noted that in the syntax descriptors used herein, the following descriptors may be applied:

-   -   b(8): byte having any pattern of bit string (8 bits). The         parsing process for this descriptor is specified by the return         value of the function read_bits(8).     -   f(n): fixed-pattern bit string using n bits written (from left         to right) with the left bit first. The parsing process for this         descriptor is specified by the return value of the function         read_bits(n).     -   se(v): signed integer 0-th order Exp-Golomb-coded syntax element         with the left bit first.     -   tb(v): truncated binary using up to maxVal bits with maxVal         defined in the semantics of the symtax element.     -   tu(v): truncated unary using up to maxVal bits with maxVal         defined in the semantics of the symtax element.     -   u(n): unsigned integer using n bits. When n is “v” in the syntax         table, the number of bits varies in a manner dependent on the         value of other syntax elements. The parsing process for this         descriptor is specified by the return value of the function         read_bits(n) interpreted as a binary representation of an         unsigned integer with most significant bit written first.     -   ue(v): unsigned integer 0-th order Exp-Golomb-coded syntax         element with the left bit first.

As described above, video content includes video sequences comprised of a series of pictures and each picture may be divided into one or more regions. In WET-Q2001, a coded representation of a picture comprises VCL NAL units of a particular layer within an AU and contains all CTUs of the picture. For example, referring again to FIG. 2 , the coded representation of Pic₃ is encapsulated in three coded slice NAL units (i.e., Slice₀ NAL unit, Slice₁ NAL unit, and Slice₂ NAL unit). It should be noted that the term video coding layer (VCL) NAL unit is used as a collective term for coded slice NAL units, i.e., VCL NAL is a collective term which includes all types of slice NAL units. As described above, and in further detail below, a NAL unit may encapsulate metadata used for decoding video data. A NAL unit encapsulating metadata used for decoding a video sequence is generally referred to as a non-VCL NAL unit. Thus, in WET-Q2001, a NAL unit may be a VCL NAL unit or a non-VCL NAL unit. It should be noted that a VCL NAL unit includes slice header data, which provides information used for decoding the particular slice. Thus, in WET-Q2001, information used for decoding video data, which may be referred to as metadata in some cases, is not limited to being included in non-VCL NAL units. WET-Q2001 provides where a picture unit (PU) is a set of NAL units that are associated with each other according to a specified classification rule, are consecutive in decoding order, and contain exactly one coded picture and where an access unit (AU) is a set of PUs that belong to different layers and contain coded pictures associated with the same time for output from the DPB. WET-Q2001 further provides where a layer is a set of VCL NAL units that all have a particular value of a layer identifier and the associated non-VCL NAL units. Further, in WET-Q2001, a PU consists of zero or one PH NAL units, one coded picture, which comprises of one or more VCL NAL units, and zero or more other non-VCL NAL units. Further, in WET-Q2001, a coded video sequence (CVS) is a sequence of AUs that consists, in decoding order, of a CVSS AU, followed by zero or more AUs that are not CVSS AUs, including all subsequent AUs up to but not including any subsequent AU that is a CVSS AU, where a coded video sequence start (CVSS) AU is an AU in which there is a PU for each layer in the CVS and the coded picture in each present picture unit is a coded layer video sequence start (CLVSS) picture. In WET-Q2001, a coded layer video sequence (CLVS) is a sequence of PUs within the same layer that consists, in decoding order, of a CLVSS PU, followed by zero or more PUs that are not CLVSS PUs, including all subsequent PUs up to but not including any subsequent PU that is a CLVSS PU. This is, in WET-Q2001, a bitstream may be described as including a sequence of AUs forming one or more CVSs.

Multi-layer video coding enables a video presentation to be decoded/displayed as a presentation corresponding to a base layer of video data and decoded/displayed one or more additional presentations corresponding to enhancement layers of video data. For example, a base layer may enable a video presentation having a basic level of quality (e.g., a High Definition rendering and/or a 30 Hz frame rate) to be presented and an enhancement layer may enable a video presentation having an enhanced level of quality (e.g., an Ultra High Definition rendering and/or a 60 Hz frame rate) to be presented. An enhancement layer may be coded by referencing a base layer. That is, for example, a picture in an enhancement layer may be coded (e.g., using inter-layer prediction techniques) by referencing one or more pictures (including scaled versions thereof) in a base layer. It should be noted that layers may also be coded independent of each other. In this case, there may not be inter-layer prediction between two layers. Each NAL unit may include an identifier indicating a layer of video data the NAL unit is associated with. As described above, a sub-bitstream extraction process may be used to only decode and display a particular region of interest of a picture. Further, a sub-bitstream extraction process may be used to only decode and display a particular layer of video. Sub-bitstream extraction may refer to a process where a device receiving a compliant or conforming bitstream forms a new compliant or conforming bitstream by discarding and/or modifying data in the received bitstream. For example, sub-bitstream extraction may be used to form a new compliant or conforming bitstream corresponding to a particular representation of video (e.g., a high quality representation).

In JVET-Q2001, each of a video sequence, a GOP, a picture, a slice, and CTU may be associated with metadata that describes video coding properties and some types of metadata an encapsulated in non-VCL NAL units. JVET-Q2001 defines parameters sets that may be used to describe video data and/or video coding properties. In particular, JVET-Q2001 includes the following four types of parameter sets: video parameter set (VPS), sequence parameter set (SPS), picture parameter set (PPS), and adaption parameter set (APS), where a SPS applies to apply to zero or more entire CVSs, a PPS applies to zero or more entire coded pictures, a APS applies to zero or more slices, and a VPS may be optionally referenced by a SPS. A PPS applies to an individual coded picture that refers to it. In JVET-Q2001, parameter sets may be encapsulated as a non-VCL NAL unit and/or may be signaled as a message. JVET-Q2001 also includes a picture header (PH) which is encapsulated as a non-VCL NAL unit. In JVET-Q2001, a picture header applies to all slices of a coded picture. JVET-Q2001 further enables decoding capability information (DCI) and supplemental enhancement information (SEI) messages to be signaled. In JVET-Q2001, DCI and SEI messages assist in processes related to decoding, display or other purposes, however, DCI and SEI messages may not be required for constructing the luma or chroma samples according to a decoding process. In JVET-Q2001, DCI and SEI messages may be signaled in a bitstream using non-VCL NAL units. Further, DCI and SEI messages may be conveyed by some mechanism other than by being present in the bitstream (i.e., signaled out-of-band).

FIG. 3 illustrates an example of a bitstream including multiple CVSs, where a CVS includes AUs, and AUs include picture units. The example illustrated in FIG. 3 corresponds to an example of encapsulating the slice NAL units illustrated in the example of FIG. 2 in a bitstream. In the example illustrated in FIG. 3 , the corresponding picture unit for Pic₃ includes the three VCL NAL coded slice NAL units, i.e., Slice₀ NAL unit, Slice₁ NAL unit, and Slice₂ NAL unit and two non-VCL NAL units, i.e., a PPS NAL Unit and a PH NAL unit. It should be noted that in FIG. 3 , HEADER is a NAL unit header (i.e., not to be confused with a slice header). Further, it should be noted that in FIG. 3 , other non-VCL NAL units, which are not illustrated may be included in the CVSs, e.g., SPS NAL units, VPS NAL units, SEI message NAL units, etc. Further, it should be noted that in other examples, a PPS NAL Unit used for decoding Pic₃ may be included elsewhere in the bitstream, e.g., in the picture unit corresponding to Pic₀ or may be provided by an external mechanism. As described in further detail below, in JVET-Q2001, a PH syntax structure may be present in the slice header of a VCL NAL unit or in a PH NAL unit of the current PU.

JVET-Q2001 defines NAL unit header semantics that specify the type of Raw Byte Sequence Payload (RBSP) data structure included in the NAL unit. Table 1 illustrates the syntax of the NAL unit header provided in JVET-Q2001.

TABLE 1 Descriptor nal_unit_header( ) {  forbidden_zero_bit f(1)  nuh_reserved_zero_bit u(1)  nuh_layer_id u(6)  nal_unit_type u(5)  nuh_temporal_id_plus1 u(3) }

JVET-Q2001 provides the following definitions for the respective syntax elements illustrated in Table 1.

-   forbidden_zero_bit shall be equal to 0. -   nuh_reserved_zero_bit shall be equal to ‘0’. The value 1 of     nuh_reserved_zero_bit may be specified in the future by ITU-T |     ISO/IEC. Decoders shall ignore (i.e. remove from the bitstream and     discard) NAL units with nuh_reserved_zero_bit equal to ‘1’. -   nuh_layer_id specifies the identifier of the layer to which a VCL     NAL unit belongs or the identifier of a layer to which a non-VCL NAL     unit applies. The value of nuh_layer_id shall be in the range of 0     to 55, inclusive. Other values for nuh_layer_id are reserved for     future use by ITU-T | ISO/IEC. -   The value of nuh_layer_id shall be the same for all VCL NAL units of     a coded picture. The value of nuh_layer_id of a coded picture or a     PU is the value of the nuh_layer_id of the VCL NAL units of the     coded picture or the PU. -   The value of nuh_layer_id for AUD, PH, EOS, and FD NAL units is     constrained as follows:     -   If nal_unit_type is equal to AUD_NUT, nuh_layer_id shall be         equal to vps_layer_id[0 ].     -   Otherwise, when nal_unit_type is equal to PH_NUT, EOS_NUT, or         FD_NUT, nuh_layer_id shall be equal to the nuh_layer_id of         associated VCL NAL unit.     -   NOTE —The value of nuh_layer_id of DCI, VPS, and EOB NAL units         is not constrained. -   The value of nal_unit_type shall be the same for all pictures of a     CVSS AU. -   nuh_temporal_id_plus1 minus 1 specifies a temporal identifier for     the NAL unit. -   The value of nuh_temporal_id_plus1 shall not be equal to 0. -   The variable TemporalId is derived as follows:

TemporalId=nuh_temporal_id_plus1−1

-   When nal_unit_type is in the range of IDR_W_RADL to RSV_IRAP_12,     inclusive, TemporalId shall be equal to 0. -   When nal_unit_type is equal to STSA_NUT and     vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is equal     to 1, TemporalId shall not be equal to 0. -   The value of TemporalId shall be the same for all VCL NAL units of     an AU. The value of TemporalId of a coded picture, a PU, or an AU is     the value of the TemporalId of the VCL NAL units of the coded     picture, PU, or AU. The value of TemporalId of a sublayer     representation is the greatest value of TemporalId of all VCL NAL     units in the sublayer representation. -   The value of TemporalId for non-VCL NAL units is constrained as     follows: -   If nal_unit_type is equal to DCI_NUT, VPS_NUT, or SPS_NUT,     TemporalId shall be equal to 0 and the TemporalId of the AU     containing the NAL unit shall be equal to 0. -   Otherwise, if nal_unit_type is equal to PH NUT, TemporalId shall be     equal to the TemporalId of the PU containing the NAL unit. -   Otherwise, if nal_unit_type is equal to EOS_NUT or EOB_NUT,     TemporalId shall be equal to 0. -   Otherwise, if nal_unit_type is equal to AUD_NUT, FD_NUT,     PREFIX_SEI_NUT, or SUFFIX_SEI_NUT, TemporalId shall be equal to the     TemporalId of the AU containing the NAL unit. -   Otherwise, when nal_unit_type is equal to PPS_NUT, PREFIX_APS_NUT,     or SUFFIX_APS_NUT, TemporalId shall be greater than or equal to the     TemporalId of the PU containing the NAL unit. -   NOTE—When the NAL unit is a non-VCL NAL unit, the value of     TemporalId is equal to the minimum value of the TemporalId values of     all AUs to which the non-VCL NAL unit applies. When nal_unit_type is     equal to PPS_NUT, PREFIX_APS_NUT, or SUFFIX_APS_NUT, TemporalId may     be greater than or equal to the TemporalId of the containing AU, as     all PPSs and APSs may be included in the beginning of the bitstream     (e.g., when they are transported out-of-band, and the receiver     places them at the beginning of the bitstream), wherein the first     coded picture has TemporalId equal to 0. -   nal_unit_type specifies the NAL unit type, i.e., the type of RBSP     data structure contained in the NAL unit as specified in Table 2. -   NAL units that have nal_unit_type in the range of UNSPEC28.     UNSPEC31, inclusive, for which semantics are not specified, shall     not affect the decoding process specified in this Specification. -   NOTE—NAL unit types in the range of UNSPEC28. UNSPEC31 may be used     as determined by the application. No decoding process for these     values of nal_unit_type is specified in this Specification. Since     different applications might use these NAL unit types for different     purposes, particular care must be exercised in the design of     encoders that generate NAL units with these nal_unit_type values,     and in the design of decoders that interpret the content of NAL     units with these nal_unit_type values. This Specification does not     define any management for these values. These nal_unit_type values     might only be suitable for use in contexts in which “collisions” of     usage (i.e., different definitions of the meaning of the NAL unit     content for the same nal_unit_type value) are unimportant, or not     possible, or are managed—e.g., defined or managed in the controlling     application or transport specification, or by controlling the     environment in which bitstreams are distributed. -   For purposes other than determining the amount of data in the     decoding units of the bitstream, decoders shall ignore (remove from     the bitstream and discard) the contents of all NAL units that use     reserved values of nal_unit_type. -   NOTE—This requirement allows future definition of compatible     extensions to this Specification.

TABLE 2 Name of Content of NAL unit and RBSP syntax NAL unit nal_unit_type nal_unit_type structure type class 0 TRAIL_NUT Coded slice of a trailing picture VCL slice_layer_rbsp( ) 1 STSA_NUT Coded slice of an STSA picture VCL slice_layer_rbsp( ) 2 RADL_NUT Coded slice of a RADL picture VCL slice_layer_rbsp( ) 3 RASL_NUT Coded slice of a RASL picture VCL slice_layer_rbsp( ) 4 . . . 6 RSV_VCL_4 . . . Reserved non-IRAP VCL NAL unit types VCL RSV_VCL_6 7 IDR_W_RADL Coded slice of an IDR picture VCL 8 IDR_N_LP slice_layer_rbsp( ) 9 CRA_NUT Coded slice of a CRA picture VCL silce_layer_rbsp( ) 10 GDR_NUT Coded slice of a GDR picture VCL slice_layer_rbsp( ) 11 RSV_IRAP_11 Reserved IRAP VCL NAL unit types VCL 12 RSV_IRAP_12 13 DCI_NUT Decoding capability information non-VCL decoding_capability_information_rbsp( ) 14 VPS_NUT Video parameter set non-VCL video_parameter_set_rbsp( ) 15 SPS_NUT Sequence parameter set non-VCL seq_parameter_set_rbsp( ) 16 PPS_NUT Picture parameter set non-VCL pic_parameter_set_rbsp( ) 17 PREFIX_APS_NUT Adaptation parameter set non-VCL 18 SUFFIX_APS_NUT adaptation_parameter_set_rbsp( ) 19 PH_NUT Picture header non-VCL picture_header_rbsp( ) 20 AUD_NUT AU delimiter non-VCL access_unit_delimiter_rbsp( ) 21 EOS_NUT End of sequence non-VCL end_of_seq_rbsp( ) 22 EOB_NUT End of bitstream non-VCL end_of_bitstream_rbsp( ) 23 PREFIX_SEI_NUT Supplemental enhancement information non-VCL 24 SUFFIX_SEI_NUT sei_rbsp( ) 25 FD_NUT Filler data non-VCL filler_data_rbsp( ) 26 RSV_NVCL_26 Reserved non-VCL NAL unit types non-VCL 27 RSV_NVCL_27 28 . . . 31 UNSPEC_28 . . . Unspecified non-VCL NAL unit types non-VCL UNSPEC_31 NOTE - A clean random access (CRA) picture may have associated RASL or RADL pictures present in the bitstream. NOTE - An instantaneous decoding refresh (IDR) picture having nal_unit_type equal to IDR_N_LP does not have associated leading pictures present in the bitstream. An IDR picture having nal_unit_type equal to IDR_W_RADL does not have associated RASL pictures present in the bitstream, but may have associated RADL pictures in the bitstream.

-   For VCL NAL units of any particular picture, the following applies:     -   If mixed_nalu_types_in_pic_flag is equal to 0, the value of         nal_unit_type shall be the same for all coded slice NAL units of         a picture. A picture or a PU is referred to as having the same         NAL unit type as the coded slice NAL units of the picture or PU.     -   Otherwise (mixed_nalu_types_in_pic_flag is equal to 1), the VCL         NAL units of one or more subpictures of the picture all have a         particular value of nal_unit_type equal to STSA NUT, RADL_NUT,         RASL_NUT, IDR_W_RADL, IDR_N_LP, or CRA_NUT, while the other VCL         NAL units in the picture all have a different particular value         of nal_unit_type equal to TRAIL_NUT, RADL_NUT, or RASL_NUT. -   For a single-layer bitstream, the following constraints apply:     -   Each picture, other than the first picture in the bitstream in         decoding order, is considered to be associated with the previous         IRAP picture in decoding order.     -   When a picture is a leading picture of an IRAP picture, it shall         be a RADL or RASL picture.     -   When a picture is a trailing picture of an IRAP picture, it         shall not be a RADL or RASL picture.     -   No RASL pictures shall be present in the bitstream that are         associated with an IDR picture.     -   No RADL pictures shall be present in the bitstream that are         associated with an IDR picture having nal_unit_type equal to         IDR_N_LP.     -   NOTE—It is possible to perform random access at the position of         an IRAP PU by discarding all PUs before the IRAP PU (and to         correctly decode the IRAP picture and all the subsequent         non-RASL pictures in decoding order), provided each parameter         set is available (either in the bitstream or by external means         not specified in this Specification) when it is referenced.     -   Any picture that precedes an IRAP picture in decoding order         shall precede the IRAP picture in output order and shall precede         any RADL picture associated with the IRAP picture in output         order.     -   Any RASL picture associated with a CRA picture shall precede any         RADL picture associated with the CRA picture in output order.     -   Any RASL picture associated with a CRA picture shall follow, in         output order, any IRAP picture that precedes the CRA picture in         decoding order.     -   If field_seq_flag is equal to 0 and the current picture is a         leading picture associated with an IRAP picture, it shall         precede, in decoding order, all non-leading pictures that are         associated with the same IRAP picture. Otherwise, let picA and         picB be the first and the last leading pictures, in decoding         order, associated with an IRAP picture, respectively, there         shall be at most one non-leading picture preceding picA in         decoding order, and there shall be no non-leading picture         between picA and picB in decoding order.

It should be noted that generally, an Intra Random Access Point (IRAP) picture is a picture that does not refer to any pictures other than itself for prediction in its decoding process. In JVET-Q2001, an IRAP picture may be a clean random access (CRA) picture or an instantaneous decoder refresh (IDR) picture. In JVET-Q2001, the first picture in the bitstream in decoding order must be an IRAP or a gradual decoding refresh (GDR) picture. JVET-Q2001 describes the concept of a leading picture, which is a picture that precedes the associated IRAP picture in output order. JVET-Q2001 further describes the concept of a trailing picture which is a non-IRAP picture that follows the associated IRAP picture in output order. Trailing pictures associated with an IRAP picture also follow the IRAP picture in decoding order. For IDR pictures, there are no trailing pictures that require reference to a picture decoded prior to the IDR picture. JVET-Q2001 provides where a CRA picture may have leading pictures that follow the CRA picture in decoding order and contain inter picture prediction references to pictures decoded prior to the CRA picture. Thus, when the CRA picture is used as a random access point these leading pictures may not be decodable and are identified as random access skipped leading (RASL) pictures. The other type of picture that can follow an IRAP picture in decoding order and precede it in output order is the random access decodable leading (RADL) picture, which cannot contain references to any pictures that precede the IRAP picture in decoding order. A GDR picture, is a picture for which each VCL NAL unit has nal_unit_type equal to GDR NUT. If the current picture is a GDR picture that is associated with a picture header which signals a syntax element recovery_poc_cnt and there is a picture picA that follows the current GDR picture in decoding order in the CLVS and that has PicOrderCntVal equal to the PicOrderCntVal of the current GDR picture plus the value of recovery_poc_cnt, the picture picA is referred to as the recovery point picture.

As provided in Table 2, a NAL unit may include a decoding capability information syntax structure. Table 3 illustrates the syntax structure of the DCI provided in JVET-Q2001.

TABLE 3 Descriptor decoding_capability_information_rbsp( ) {  dci_max_sublayers_minus1 u(3)  dci_reserved_zero_bit u(1)  dci_num_ptls_minus1 u(4)  for( i = 0; i <= dci_num_ptls_minus1; i++ )   profile_tier_level( 1, 0 )  dci_extension_flag u(1)  if( dci_extension_flag )   while( more_rbsp_data( ) )    dci_extension_data_flag u(1)  rbsp_trailing_bits( ) }

With respect to Table 3, JVET-Q2001 provides the following semantics:

-   A DCI RB SP may be made available to the decoder, through either     being present in the bitstream, included in at least the first AU of     the bitstream, or provided through external means. -   NOTE—The information contained in the DCI RB SP is not necessary for     operation of the decoding process specified in this Specification. -   When present, all DCI NAL units in a bitstream shall have the same     content. -   dci_max_sublayers_minus1 plus 1 specifies the maximum number of     temporal sublayers that may be present in a layer in each CVS of the     bitstream. The value of dci_max_sublayers_minus1 shall be in the     range of 0 to 6, inclusive. -   dci_reserved_zero_bit shall be equal to 0 in bitstreams conforming     to this version of this Specification. The value 1 for     dci_reserved_zero_bit is reserved for future use by ITU-T | ISO/IEC. -   dci_num_ptls_minus1 plus 1 specifies the number of     profile_tier_level( ) syntax structures in the DCI NAL unit. -   It is a requirement of bitstream conformance that each OLS in a CVS     in the bitstream shall conforms to at least one of the     profile_tier_level( ) syntax structures in the DCI NAL unit.     -   NOTE—The DCI NAL unit may include PTL information, possibly         carried in multiple profile_tier_level( ) syntax structures,         that applies collectively to multiple OLSs, and does not need to         include PTL information for each of the OLSs individually. -   dci_extension_flag equal to 0 specifies that no     dci_extension_data_flag syntax elements are present in the DCI RBSP     syntax structure. dci_extension_flag equal to 1 specifies that there     are dci_extension_data_flag syntax elements present in the DCI RBSP     syntax structure. -   dci_extension_data_flag may have any value. Its presence and value     do not affect decoder conformance to profiles specified below.     Decoders conforming to this version of this Specification shall     ignore all dci_extension_data_flag syntax elements.

As provided in Table 3, a DCI includes a profile tier level( ) syntax structure. Table 4 illustrates the profile_tier_level( ) syntax structure provided in JVET-Q2001.

TABLE 4 Descriptor profile_tier_level( profileTierPresentFlag, maxNumSubLayersMinus1 ) {  if( profileTierPresentFlag ) {   general_profile_idc u(7)   general_tier_flag u(1)   general_constraint_info( )  }  general_level_idc u(8)  if( profileTierPresentFlag ) {   num_sub_profiles u(8)   for( i = 0; i < num_sub_profiles; i++ )    general_sub_profile_idc[ i ] u(32)  }  for( i = 0; i < maxNumSubLayersMinus1; i++ )   sublayer_level_present_flag[ i ] u(1)  while( !byte_aligned( ) )   ptl_alignment_zero_bit f(1)  for( i = 0; i < maxNumSubLayersMinus1; i++ )   if( sublayer_level_present_flag[ i ] )    sublayer_level_idc[ i ] u(8) }

With respect to Table 4, WET-Q2001 provides the following semantics:

-   A profile_tier_level( ) syntax structure provides level information     and, optionally, profile, tier, sub-profile, and general constraints     information. -   When the profile_tier_level( ) syntax structure is included in a     VPS, the OlsInScope is one or more OLSs specified by the VPS. When     the profile_tier_level( ) syntax structure is included in an SPS,     the OlsInScope is the OLS that includes only the layer that is the     lowest layer among the layers that refer to the SPS, and this lowest     layer is an independent layer. -   general_profile_idc indicates a profile to which OlsInScope conforms     as specified. Bitstreams shall not contain values of     general_profile_idc other than those specified. Other values of     general_profile_idc are reserved for future use by ITU-T | ISO/IEC. -   general_tier_flag specifies the tier context for the interpretation     of general_level_idc as specified. -   general_level_idc indicates a level to which OlsInScope conforms as     specified. Bitstreams shall not contain values of general_level_idc     other than those specified. Other values of general_level_idc are     reserved for future use by ITU-T | ISO/IEC.     -   NOTE—A greater value of general_level_idc indicates a higher         level. The maximum level signalled in the DCI NAL unit for         OlsInScope may be higher than but cannot be lower than the level         signalled in the SPS for a CLVS contained within OlsInScope.     -   NOTE—When OlsInScope conforms to multiple profiles,         general_profile_idc should indicate the profile that provides         the preferred decoded result or the preferred bitstream         identification, as determined by the encoder (in a manner not         specified in this Specification).     -   NOTE—When the CVSs of OlsInScope conform to different profiles,         multiple profile_tier_level( ) syntax structures may be included         in the DCI NAL unit such that for each CVS of the OlsInScope         there is at least one set of indicated profile, tier, and level         for a decoder that is capable of decoding the CVS. -   num_sub_profiles specifies the number of the     general_sub_profile_idc[i ] syntax elements. -   general_sub_profile_idc[i] indicates the i-th interoperability     metadata registered as specified by Rec. ITU-T T.35, the contents of     which are not specified in this Specification. -   sublayer_level_present_flag[i ] equal to 1 specifies that level     information is present in the profile_tier_level( ) syntax structure     for the sublayer representation with TemporalId equal to i.     sublayer_level_present_flag[i ] equal to 0 specifies that level     information is not present in the profile_tier_level( ) syntax     structure for the sublayer representation with TemporalId equal to     i. -   ptl_alignment_zero_bits shall be equal to 0. -   The semantics of the syntax element sublayer_level_idc[i] is, apart     from the specification of the inference of not present values, the     same as the syntax element general_level_idc, but apply to the     sublayer representation with TemporalId equal to i. -   When not present, the value of sublayer_level_idc[i ] is inferred as     follows:     -   sublayer_level_idc[maxNumSubLayersMinus1] is inferred to be         equal to general_level_idc of the same profile_tier_level( )         structure,     -   For i from maxNumSubLayersMinus1−1 to 0 (in decreasing order of         values of i), inclusive, sublayer_level_idc[i] is inferred to be         equal to sublayer_level_idc[i+1].

As provided in Table 2, a NAL unit may include a video parameter set syntax structure and as provided above a VPS may include the profile_tier_level( ) syntax structure. Table 5 illustrates the syntax structure of the VPS provided in JVET-Q2001.

TABLE 5 Descriptor video_parameter_set_rbsp( ) {  vps_video_parameter_set_id u(4)  vps_max_layers_minus1 u(6)  vps_max_sublayers_minus1 u(3)  if( vps_max_layers_minus1 > 0 &&  vps_max_sublayers_minus1 > 0 )   vps_all_layers_same_num_sublayers_flag u(1)  if( vps_max_layers_minus1 > 0 )   vps_all_independent_layers_flag u(1)  for( i = 0; i <= vps_max_layers_minus1; i++ ) {   vps_layer_id[ i ] u(6)   if( i > 0 && !vps_all_independent_layers_flag ) {    vps_independent_layer_flag[ i ] u(1)    if( !vps_independent_layer_flag[ i ] ) {     for( j = 0; j < i; j++ )      vps_direct_ref_layer_flag[ i ][ j ] u(1)     max_tid_ref_present_flag[ i ] u(1)     if( max_tid_ref_present_flag[ i ] )      max_tid_il_ref_pics_plus1[ i ] u(3)    }   }  }  if( vps_max_layers_minus1 > 0 ) {   if( vps_all_independent_layers_flag )    each_layer_is_an_ols_flag u(1)   if( !each_layer_is_an_ols_flag ) {    if( !vps_all_independent_layers_flag )     ols_mode_idc u(2)    if( ols_mode_idc = = 2 ) {     num_output_layer_sets_minus1 u(8)     for( i = 1; i <= num_output_layer_sets_minus1; i     ++)      for( j = 0; j <= vps_max_layers_minus1; j++ )       ols_output_layer_flag[ i ][ j ] u(1)    }   }  }  vps_num_ptls_minus1 u(8)  for( i = 0; i <= vps_num_ptls_minus1; i++ ) {   if( i > 0 )    pt_present_flag[ i ] u(1)   if( vps_max_sublayers_minus1 > 0 && !vps_all_layers_same_num_sublayers_flag )    ptl_max_temporal_id[ i ] u(3)  }  while( !byte_aligned( ) )   vps_ptl_alignment_zero_bit /* equal to 0 */ f(1)  for( i = 0; i <= vps_num_ptls_minus1; i++ )   profile_tier_level( pt_present_flag[ i ],   ptl_max_temporal_id[ i ] )  for( i = 0; i < TotalNumOlss; i++ )   if( vps_num_ptls_minus1 > 0 )    ols_ptl_idx[ i ] u(8)  if( !vps_all_independent_layers_flag )   vps_num_dpb_params ue(v)  if( vps_num_dpb_params > 0 &&  vps_max_sublayers_minus1 > 0 )   vps_sublayer_dpb_params_present_flag u(1)  for( i = 0; i < vps_num_dpb_params; i++ ) {   if( vps_max_sublayers_minus1 > 0 && !vps_all_layers_same_num_sublayers_flag )    dpb_max_temporal_id[ i ] u(3)   dpb_parameters( dpb_max_temporal_id[ i ], vps_sublayer_dpb_params_present_flag )  }  for( i = 0; i < TotalNumOlss; i++ ) {   if( NumLayersInOls[ i ] > 1 ) {    ols_dpb_pic_width[ i ] ue(v)    ols_dpb_pic_height[ i ] ue(v)    if( vps_num_dpb_params > 1 )     ols_dpb_params_idx[ i ] ue(v)   }  }  if( !each_layer_is_an_ols_flag )   vps_general_hrd_params_present_flag u(1)  if( vps_general_hrd_params_present_flag ) {   general_hrd_parameters( )   if( vps_max_sublayers_minus1 > 0 )    vps_sublayer_cpb_params_present_flag u(1)   num_ols_hrd_params_minus1 ue(v)   for( i = 0; i <= num_ols_hrd_params_minus1; i++ ) {    if( vps_max_sublayers_minus1 > 0 && !vps_all_layers_same_num_sublayers_flag )     hrd_max_tid[ i ] u(3)    firstSubLayer = vps_sublayer_cpb_params_present_flag ? 0 : hrd_max_tid[ i ]    ols_hrd_parameters( firstSubLayer, hrd_max_tid[ i ]    )   }   if( num_ols_hrd_params_minus1 + 1 !=     TotalNumOlss && num_ols_hrd_params_minus1     > 0 )    for( i = 1; i < TotalNumOlss; i++ )     if( NumLayersInOls[ i ] > 1 )      ols_hrd_idx[ i ] ue(v)  }  vps_extension_flag u(1)  if( vps_extension_flag )   while( more_rbsp_data( ) )    vps_extension_data_flag u(1)  rbsp_trailing_bits( ) }

With respect to Table 5, JVET-Q2001 provides the following semantics:

-   A VPS RBSP shall be available to the decoding process prior to it     being referenced, included in at least one AU with TemporalId equal     to 0 or provided through external means. -   All VPS NAL units with a particular value of     vps_video_parameter_set_id in a CVS shall have the same content. -   vps_video_parameter_set_id provides an identifier for the VPS for     reference by other syntax elements. The value of     vps_video_parameter_set_id shall be greater than 0. -   vps_max_layers_minus1 plus 1 specifies the maximum allowed number of     layers in each CVS referring to the VPS. -   vps_max_sublayers_minus1 plus 1 specifies the maximum number of     temporal sublayers that may be present in a layer in each CVS     referring to the VPS. The value of vps_max_sublayers_minus1 shall be     in the range of 0 to 6, inclusive. -   vps_all_layers_same_num_sublayers_flag equal to 1 specifies that the     number of temporal sublayers is the same for all the layers in each     CVS referring to the VPS. vps_all_layers_same_num_sublayers_flag     equal to 0 specifies that the layers in each CVS referring to the     VPS may or may not have the same number of temporal sublayers. When     not present, the value of vps_all_layers_same_num_sublayers_flag is     inferred to be equal to 1. -   vps_all_independent_layers_flag equal to 1 specifies that all layers     in the CVS are independently coded without using inter-layer     prediction. vps_all_independent_layers_flag equal to 0 specifies     that one or more of the layers in the CVS may use inter-layer     prediction. When not present, the value of     vps_all_independent_layers_flag is inferred to be equal to 1. -   vps_layer_id[i] specifies the nuh_layer_id value of the i-th layer.     For any two non-negative integer values of m and n, when m is less     than n, the value of vps_layer_id[m] shall be less than     vps_layer_id[n]. -   vps_independent_layer_flag[i] equal to 1 specifies that the layer     with index i does not use inter-layer prediction.     vps_independent_layer_flag[i] equal to 0 specifies that the layer     with index i may use inter-layer prediction and the syntax elements     vps_direct_ref_layer_flag[i][j] for j in the range of 0 to i−1,     inclusive, are present in VPS. When not present, the value of     vps_independent_layer_flag[i] is inferred to be equal to 1. -   vps_direct_ref_layer_flag[i][j] equal to 0 specifies that the layer     with index j is not a direct reference layer for the layer with     index i. vps_direct_ref_layer_flag [i][j] equal to 1 specifies that     the layer with index j is a direct reference layer for the layer     with index i. When vps_direct_ref_layer_flag[i][j] is not present     for i and j in the range of 0 to vps_max_layers_minus1, inclusive,     it is inferred to be equal to 0. When vps_independent_layer_flag[i]     is equal to 0, there shall be at least one value of j in the range     of 0 to i−1, inclusive, such that the value of     vps_direct_ref_layer_flag[i][j] is equal to 1. -   The variables NumDirectRefLayers[i], DirectRefLayerIdx[i][d],     NumRefLayers[i], RefLayerIdx[i][r], and LayerUsedAsRefLayerFlag[j]     are derived as follows:

for( i = 0; i <= vps_max_layers_minus1; i++ ) {  for( j = 0; j <= vps_max_layers_minus1; j++ ) {   dependencyFlag[ i ][ j ] = vps_direct_ref_layer_flag[ i ][ j ]   for( k = 0; k < i; k++ )    if( vps_direct_ref_layer_flag[ i ][ k ] && dependencyFlag[ k ][ j ] )     dependencyFlag[ i ][ j ] = 1  }  LayerUsedAsRefLayerFlag[ i ] = 0 } for( i = 0; i <= vps_max_layers_minus1; i++ ) {  for( j = 0, d = 0, r = 0; j <= vps_max_layers_minus1; j++ ) {   if( vps_direct_ref_layer_flag[ i ][ j ] ) {    DirectRefLayerIdx[ i ][ d++ ] = j    LayerUsedAsRefLayerFlag[ j ] = 1   }   if( dependency Flag[ i ][ j ] )    RefLayerIdx[ i ][ r++ ] = j  }  NumDirectRefLayers[ i ] = d  NumRefLayers[ i ] = r }

-   The variable GeneralLayerIdx[i], specifying the layer index of the     layer with nuh_layer_id equal to vps_layer_id[i], is derived as     follows:

for( i = 0; i <= vps_max_layers_minus1; i++ )  GeneralLayerIdx[ vps_layer_id[ i ] ] = i

-   For any two different values of i and j, both in the range of 0 to     vps_max_layers_minus1, inclusive, when dependencyFlag[i][j] equal to     1, it is a requirement of bitstream conformance that the values of     chroma_format_idc and bit_depth_minus8 that apply to the i-th layer     shall be equal to the values of chroma_format_idc and     bit_depth_minus8, respectively, that apply to the j-th layer. -   max_tid_ref_present_flag[i] equal to 1 specifies that the syntax     element max_tid_ref_pics_plus1[i] is present.     max_tid_ref_present_flag[i] equal to 0 specifies that the syntax     element max_tid_il_ref_pics_plus1[i] is not present. -   max_tid_il_ref_pics_plus1[i] equal to 0 specifies that inter-layer     prediction is not used by non-IRAP pictures of the i-th layer.     max_tid_il_ref_pics_plus1[i] greater than 0 specifies that, for     decoding pictures of the i-th layer, no picture with TemporalId     greater than max_tid_il_ref_pics_plus1[i]−1 is used as ILRP. When     not present, the value of max_tid_il_ref_pics_plus1[i] is inferred     to be equal to 7. -   each_layer_is_an_ols_flag equal to 1 specifies that each OLS     contains only one layer and each layer itself in a CVS referring to     the VPS is an OLS with the single included layer being the only     output layer. each_layer_is_an_ols_flag equal to 0 that an OLS may     contain more than one layer. If vps_max_layers_minus1 is equal to 0,     the value of each_layer_is_an_ols_flag is inferred to be equal to 1.     Otherwise, when vps_all_independent_layers_flag is equal to 0, the     value of each_layer_is_an_ols_flag is inferred to be equal to 0. -   ols_mode_idc equal to 0 specifies that the total number of OLSs     specified by the VPS is equal to vps_max_layers_minus1+1, the i-th     OLS includes the layers with layer indices from 0 to i, inclusive,     and for each OLS only the highest layer in the OLS is output. -   ols_mode_idc equal to 1 specifies that the total number of OLSs     specified by the VPS is equal to vps_max_layers_minus1+1, the i-th     OLS includes the layers with layer indices from 0 to i, inclusive,     and for each OLS all layers in the OLS are output. -   ols_mode_idc equal to 2 specifies that the total number of OLSs     specified by the VPS is explicitly signalled and for each OLS the     output layers are explicitly signalled and other layers are the     layers that are direct or indirect reference layers of the output     layers of the OLS. -   The value of ols_mode_idc shall be in the range of 0 to 2,     inclusive. The value 3 of ols_mode_idc is reserved for future use by     ITU-T ISO/IEC. -   When vps_all_independent_layers_flag is equal to 1 and     each_layer_is_an_ols_flag is equal to 0, the value of ols_mode_idc     is inferred to be equal to 2. -   num_output_layer_sets_minus1 plus 1 specifies the total number of     OLSs specified by the VPS when ols_mode_idc is equal to 2. -   The variable TotalNumOlss, specifying the total number of OLSs     specified by the VPS, is derived as follows:

if(vps_max_layers_minus1 = = 0 )  TotalNumOlss = 1 else if( each_layer_is_an_ols_flag ∥ ols_mode_idc = = 0 ∥ ols_mode_idc = = 1 )  TotalNumOlss = vps_max_layers_minus1 + 1 else if( ols_mode_idc = = 2 )  TotalNumOlss = num_output_layer_sets_minus1 + 1

-   ols_output_layer_flag[i][j] equal to 1 specifies that the layer with     nuh_layer_id equal to vps_layer_id[j] is an output layer of the i-th     OLS when ols_mode_idc is equal to 2. ols_output_layer_flag[i][j]     equal to 0 specifies that the layer with nuh_layer_id equal to     vps_layer_id[j] is not an output layer of the i-th OLS when     ols_mode_idc is equal to 2. -   The variable NumOutputLayersInOls[i], specifying the number of     output layers in the i-th OLS, the variable     NumSubLayersInLayerInOLS[i][j], specifying the number of sublayers     in the j-th layer in the i-th OLS, the variable     OutputLayerIdInOls[i][j], specifying the nuh_layer_id value of the     j-th output layer in the i-th OLS, and the variable     LayerUsedAsOutputLayerFlag[k], specifying whether the k-th layer is     used as an output layer in at least one OLS, are derived as follows:

NumOutputLayersInOls[ 0 ] = 1 OutputLayerIdInOls[ 0 ][ 0 ] = vps_layer_id[ 0 ] NumSubLayersInLayerInOLS[ 0 ][ 0 ] = vps_max_sub_layers_minus1 + 1 LayerUsedAsOutputLayerFlag[ 0 ] = 1 for( i = 1, i <= vps_max_layers_minus1; i++ ) {  if( each_layer_is_an_ols_flag ols_mode_idc < 2 )   LayerUsedAsOutputLayerFlag[ i ] = 1  else/*( !each_layer_is_an_ols_flag && ols_mode_idc == 2)*/   LayerUsedAsOutputLayerFlag[ i ] = 0 } for( i = 1; i < TotalNumOlss; i++ )  if( each_layer_is_an_ols_flag ols_mode_idc = = 0 ) {   NumOutputLayersInOls[ i ] = 1   OutputLayerIdInOls[ i ][ 0 ] = vps_layer_id[ i ]   for( j = 0; j < i && ( ols_mode_idc = = 0 ); j++ )    NumSubLayersInLayerInOLS[ i ][ j ] = max_tid_il_ref_pics_plus1[ i ]   NumSubLayersInLayerInOLS[ i ][ i ] = vps_max_sub_layers_minus1 + 1  } else if( ols_mode_idc = = 1) {   NumOutputLayersInOls[ i ] = i + 1   for( j = 0; j < NumOutputLayersInOls[ i ]j++ ) {    OutputLayerIdInOls[ i ][ j ] = vps_layer_id[ j ]    NumSubLayersInLayerInOLS[ i ][ j ] = vps_max_sub_layers_minus1 + 1   }  } else if( ols_mode_idc = = 2 ) {   for( j = 0; j <= vps_max_layers_minus1; j++ ) {    layerIncludedInOlsFlag[ i ][ j ] = 0    NumSubLayersInLayerInOLS[ i ][ j ] = 0   }   for( k = 0, j = 0; k <= vps_max_layers_minus1; k++ )    if( ols_output_layer_flag[ i ][ k ] ) {     layerIncludedInOlsFlag[ i ][ k ] = 1     LayerUsedAsOutputLayerFlag[ k ] = 1     OutputLayerIdx[ i ][ j ] = k     OutputLayerIdInOls[ i ][ j++ ] = vps_layer_id[ k ]     NumSubLayersInLayerInOLS[ i ][ j ] = vps_max_sub_layers_minus1 + 1    }   NumOutputLayersInOls[ i ] = j   for( j = 0; j < NumOutputLayersInOls[ i ]; j++ ) {    idx = OutputLayerIdx[ i ][ j ]    for( k = 0; k < NumRefLayers idx ]; k++ ) {     layerIncludedInOlsFlag[ i ][ RefLayerIdx[ idx ][ k ] ] = 1     if(NumSubLayersInLayerInOLS[ i ][ RefLayerIdx[ idx ][ k ] ] <      max_tid_il_ref_pics_plus1[ OutputLayerIdInOls[ i ][ j ] ] )     NumSubLayersInLayerInOLS[ i ][ RefLayerIdx[ idx ][ k ] ] =      max_tid_il_ref_pics_plus1[ OutputLayerIdInOls[ i ][ j ] ]    }   }  }

-   For each value of i in the range of 0 to vps_max_layers_minus1,     inclusive, the values of LayerUsedAsRefLayerFlag[i] and     LayerUsedAsOutputLayerFlag[i] shall not be both equal to 0. In other     words, there shall be no layer that is neither an output layer of at     least one OLS nor a direct reference layer of any other layer. -   For each OLS, there shall be at least one layer that is an output     layer. In other words, for any value of i in the range of 0 to     TotalNumOlss−1, inclusive, the value of NumOutputLayersInOls[i]     shall be greater than or equal to 1.

The variable NumLayersInOls[i], specifying the number of layers in the i-th OLS, and the variable LayerIdInOls[i][j], specifying the nuh_layer_id value of the j-th layer in the i-th OLS, are derived as follows:

NumLayersInOls[ 0 ] = 1 LayerIdInOls[ 0 ][ 0 ] = vps_layer_id[ 0 ] for( i = 1; i < TotalNumOlss; i++ ) {  if( each_layer_is_an_ols_flag) {   NumLayersInOls[ i ] = 1   LayerIdInOls[ i ][ 0 ] = vps_layer_id[ i ]   } else if( ols_mode_idc = = 0 ols_mode_idc = = 1 ) {   NumLayersInOls[ i ] = i + 1   for( j = 0; j < NumLayersInOls[ i ]; j++ )    LayerIdInOls[ i ][ j ] = vps_layer_id[ j ]  } else if( ols_mode_idc = = 2 ) {   for( k = 0, j = 0; k <= vps_max_layers_minus1; k++ )    if( layerIncludedInOlsFlag[ i ][ k ] )     LayerIdInOls[ i ][ j++ ] = vps_layer_id[ k ]   NumLayersInOls[ i ] = j  } } NOTE The 0-th OLS contains only the lowest layer (i.e., the layer with nuh_layer_id equal to vps_layer_id[ 0 ]) and for the 0-th OLS the only included layer is output.

-   The variable OlsLayerIdx[i][j], specifying the OLS layer index of     the layer with nuh_layer_id equal to LayerIdInOls[i][j], is derived     as follows:

for( i = 0; i < TotalNumOlss; i++ )  for j = 0; j < NumLayersInOls[ i ]; j++ )   OlsLayerIdx[ i ][ LayerIdInOls[ i ][ j ] ] = j

-   The lowest layer in each OLS shall be an independent layer. In other     words, for each i in the range of 0 to TotalNumOlss-1, inclusive,     the value of     vps_independent_layer_flag[GeneralLayerIdx[LayerIdInOls[i][0]]]     shall be equal to 1. -   Each layer shall be included in at least one OLS specified by the     VPS. In other words, for each layer with a particular value of     nuh_layer_id nuhLayerId equal to one of vps_layer_id[k] fork in the     range of 0 to vps_max_layers_minus1, inclusive, there shall be at     least one pair of values of i and j, where i is in the range of 0 to     TotalNumOlss−1, inclusive, and j is in the range of     NumLayersInOls[i]-1, inclusive, such that the value of     LayerIdInOls[i][j] is equal to nuhLayerId. -   vps_num_ptls_minus1 plus 1 specifies the number of     profile_tier_level( ) syntax structures in the VPS. The value of     vps_num_ptls_minus1 shall be less than TotalNumOlss. -   pt_present_flag[i] equal to 1 specifies that profile, tier, and     general constraints information are present in the i-th     profile_tier_level( ) syntax structure in the VPS.     pt_present_flag[i] equal to 0 specifies that profile, tier, and     general constraints information are not present in the i-th     profile_tier_level( ) syntax structure in the VPS. The value of     pt_present_flag[0] is inferred to be equal to 1. When     pt_present_flag[i] is equal to 0, the profile, tier, and general     constraints information for the i-th profile_tier_level( ) syntax     structure in the VPS are inferred to be the same as that for the     (i-1)-th profile_tier_level( ) syntax structure in the VPS. -   ptl_max_temporal_id[i] specifies the TemporalId of the highest     sublayer representation for which the level information is present     in the i-th profile_tier_level( ) syntax structure in the VPS. The     value of ptl_max_temporal_id[i] shall be in the range of 0 to     vps_max_sublayers_minus1, inclusive. When vps_max_sublayers_minus1     is equal to 0, the value of ptl_max_temporal_id[i] is inferred to be     equal to 0. When vps_max_sublayers_minus1 is greater than 0 and     vps_all_layers_same_num_sublayers_flag is equal to 1, the value of     ptl_max_temporal_id[i] is inferred to be equal to     vps_max_sublayers_minus1. -   vps_ptl_alignment_zero_bit shall be equal to 0. -   ols_ptl_idx[i] specifies the index, to the list of     profile_tier_level( ) syntax structures in the VPS, of the     profile_tier_level( ) syntax structure that applies to the i-th OLS.     When present, the value of ols_ptl_idx[i] shall be in the range of 0     to vps_num_ptls_minus1, inclusive. When vps_num_ptls_minus1 is equal     to 0, the value of ols_ptl_idx[i] is inferred to be equal to 0. -   When NumLayersInOls[i] is equal to 1, the profile_tier_level( )     syntax structure that applies to the i-th OLS is also present in the     SPS referred to by the layer in the i-th OLS. It is a requirement of     bitstream conformance that, when NumLayersInOls[i] is equal to 1,     the profile_tier_level( ) syntax structures signalled in the VPS and     in the SPS for the i-th OLS shall be identical. -   vps_num_dpb_params specifies the number of dpb_parameters( ) syntax     strutcures in the VPS. The value of vps_num_dpb_params shall be in     the range of 0 to 16, inclusive. When not present, the value of     vps_num_dpb_params is inferred to be equal to 0. -   vps_sublayer_dpb_params_present_flag is used to control the presence     of max_dec_pic_buffering_minus1[ ], max_num_reorder_pics[ ], and     max_latency_increase_plus1[ ] syntax elements in the dpb_parameters(     ) syntax strucures in the VPS. When not present,     vps_sub_dpb_params_info_present_flag is inferred to be equal to 0. -   dpb_max_temporal_id[i] specifies the TemporalId of the highest     sublayer representation for which the DPB parameters may be present     in the i-th dpb_parameters( ) syntax strutcure in the VPS. The value     of dpb_max_temporal_id[i] shall be in the range of 0 to     vps_max_sublayers_minus1, inclusive. When vps_max_sublayers_minus1     is equal to 0, the value of dpb_max_temporal_id[i] is inferred to be     equal to 0. When vps_max_sublayers_minus1 is greater than 0 and     vps_all_layers_same_num_sublayers_flag is equal to 1, the value of     dpb_max_temporal_id[i] is inferred to be equal to     vps_max_sublayers_minus1. -   ols_dpb_pic_width[i] specifies the width, in units of luma samples,     of each picture storage buffer for the i-th OLS. -   ols_dpb_pic_height[i] specifies the height, in units of luma     samples, of each picture storage buffer for the i-th OLS. -   ols_dpb_params_idx[i] specifies the index, to the list of     dpb_parameters( ) syntax structures in the VPS, of the     dpb_parameters( ) syntax structure that applies to the i-th OLS when     NumLayersInOls[i] is greater than 1. When present, the value of     ols_dpb_params_idx[i] shall be in the range of 0 to     vps_num_dpb_params−1, inclusive. When ols_dpb_params_idx[i] is not     present, the value of ols_dpb_params_idx[i] is inferred to be equal     to 0. -   When NumLayersInOls[i] is equal to 1, the dpb_parameters( ) syntax     structure that applies to the i-th OLS is present in the SPS     referred to by the layer in the i-th OLS. -   vps_general_hrd_params_present_flag equal to 1 specifies that the     VPS contains a general_hrd_parameters( ) syntax structure and other     HRD parameters. vps_general_hrd_params_present_flag equal to 0     specifies that the VPS does not contain a general_hrd_parameters( )     syntax structure or other HRD parameters. When not present, the     value of vps_general_hrd_params_present_flag is inferred to be equal     to 0. -   When NumLayersInOls[i] is equal to 1, the general_hrd_parameters( )     syntax structure and the ols_hrd_parameters( ) syntax structure that     apply to the i-th OLS are present in the SPS referred to by the     layer in the i-th OLS. -   vps_sublayer_cpb_params_present_flag equal to 1 specifies that the     i-th ols_hrd_parameters( ) syntax structure in the VPS contains HRD     parameters for the sublayer representations with TemporalId in the     range of 0 to hrd_max_tid[i], inclusive.     vps_sublayer_cpb_params_present_flag equal to 0 specifies that the     i-th ols_hrd_parameters( ) syntax structure in the VPS contains HRD     parameters for the sublayer representation with TemporalId equal to     hrd_max_tid[i] only. When vps_max_sublayers_minus1 is equal to 0,     the value of vps_sublayer_cpb_params_present_flag is inferred to be     equal to 0. -   When vps_sublayer_cpb_params_present_flag is equal to 0, the HRD     parameters for the sublayer representations with TemporalId in the     range of 0 to hrd_max_tid[i]−1, inclusive, are inferred to be the     same as that for the sublayer representation with TemporalId equal     to hrd_max_tid[i]. These include the HRD parameters starting from     the fixed_pic_rate_general_flag[i] syntax element till the     sublayer_hrd_parameters(i) syntax structure immediately under the     condition “if(general_vcl_hrd_params_present_flag)” in the     ols_hrd_parameters syntax structure. -   num_ols_hrd_params_minus1 plus 1 specifies the number of     ols_hrd_parameters( ) syntax structures present in the VPS when     vps_general_hrd_params_present_flag is equal to 1. The value of     num_ols_hrd_params_minus1 shall be in the range of 0 to     TotalNumOlss−1, inclusive. -   hrd_max_tid[i] specifies the TemporalId of the highest sublayer     representation for which the HRD parameters are contained in the     i-th ols_hrd_parameters( ) syntax structure. The value of     hrd_max_tid[i] shall be in the range of 0 to     vps_max_sublayers_minus1, inclusive. When vps_max_sublayers_minus1     is equal to 0, the value of hrd_max_tid[i] is inferred to be equal     to 0. When vps_max_sublayers_minus1 is greater than 0 and     vps_all_layers_same_num_sublayers_flag is equal to 1, the value of     hrd_max_tid[i] is inferred to be equal to vps_max_sublayers_minus1. -   ols_hrd_idx[i] specifies the index, to the list of     ols_hrd_parameters( ) syntax structures in the VPS, of the     ols_hrd_parameters( ) syntax structure that applies to the i-th OLS     when NumLayersInOls[i] is greater than 1. The value of     ols_hrd_idx[[i] shall be in the range of 0 to     num_ols_hrd_params_minus1, inclusive.

When NumLayersInOls[i] is equal to 1, the ols_hrd_parameters( ) syntax structure that applies to the i-th OLS is present in the SPS referred to by the layer in the i-th OLS.

If the value of num_ols_hrd_param_minus1+1 is equal to TotalNumOlss, the value of ols_hrd_idx[i] is inferred to be equal to i. Otherwise, when NumLayersInOls[i] is greater than 1 and num_ols_hrd_params_minus1 is equal to 0, the value of ols_hrd_idx[[i] is inferred to be equal to 0.

-   vps_extension_flag equal to 0 specifies that no     vps_extension_data_flag syntax elements are present in the VPS RBSP     syntax structure. vps_extension_flag equal to 1 specifies that there     are vps_extension_data_flag syntax elements present in the VPS RBSP     syntax structure. -   vps_extension_data_flag may have any value. Its presence and value     do not affect decoder conformance to profiles specified in this     version of this Specification. Decoders conforming to this version     of this Specification shall ignore all vps_extension_data_flag     syntax elements.

As provided in Table 2, a NAL unit may include a sequence parameter set syntax structure and as provided above a SPS may include the profile_tier_level( ) syntax structure. Table 6 illustrates the syntax structure of the sequence parameter set provided in WET-Q2001.

TABLE 6 Descriptor seq_parameter_set_rbsp( ) {  sps_seq_parameter_set_id u(4)  sps_video_parameter_set_id u(4)  sps_max_sublayers_minus1 u(3)  sps_reserved_zero_4bits u(4)  sps_ptl_dpb_hrd_params_present_flag u(1)  if( sps_ptl_dpb_hrd_params_present_flag )   profile_tier_level( 1, sps_max_sublayers_minus1 )  gdr_enabled_flag u(1)  chroma_format_idc u(2)  if( chroma_format_idc = = 3 )   separate_colour_plane_flag u(1)  res_change_in_clvs_allowed_flag u(1)  pic_width_max_in_luma_samples ue(v)  pic_height_max_in_luma_samples ue(v)  sps_conformance_window_flag u(1)  if( sps_conformance_window_flag ) {   sps_conf_win_left_offset ue(v)   sps_conf_win_right_offset ue(v)   sps_conf_win_top_offset ue(v)   sps_conf_win_bottom_offset ue(v)  }  sps_log2_ctu_size_minus5 u(2)  subpic_info_present_flag u(1)  if( subpic_info_present_flag ) {   sps_num_subpics_minus1 ue(v)   sps_independent_subpics_flag u(1)   for( i = 0; sps_num_subpics_minus1 > 0 && i <= sps_num_subpics_minus1; i++ ) {    if( i > 0 && pic_width_max_in_luma_samples > CtbSizeY )     subpic_ctu_top_left_x[ i ] u(v)    if( i > 0 && pic_height_max_in_luma_samples > CtbSizeY ) {     subpic_ctu_top_left_y[ i ] u(v)    if( i < sps_num_subpics_minus1 &&      pic_width_max_in_luma_samples > CtbSizeY )     subpic_width_minus1[ i ] u(v)    if( i < sps_num_subpics_minus1 &&      pic_height_max_in_luma_samples > CtbSizeY )     subpic_height_minus1[ i ] u(v)    if( !sps_independent_subpics_flag) {     subpic_treated_as_pic_flag[ i ] u(1)     loop_filter_across_subpic_enabled_flag[ i ] u(1)    }   }   sps_subpic_id_len_minus1 ue(v)   subpic_id_mapping_explicitly_signalled_flag u(1)   if( subpic_id_mapping_explicitly_signalled_flag ) {    subpic_id_mapping_in_sps_flag u(1)    if( subpic_id_mapping_in_sps_flag )     for( i = 0; i <= sps_num_subpics_minus1; i++ )      sps_subpic_id[ i ] u(v)   }  }  bit_depth_minus8 ue(v)  sps_entropy_coding_sync_enabled_flag u(1)  if( sps_entropy_coding_sync_enabled_flag )   sps_wpp_entry_point_offsets_present_flag u(1)  sps_weighted_pred_flag u(1)  sps_weighted_bipred_flag u(1)  log2_max_pic_order_cnt_lsb_minus4 u(4)  sps_poc_msb_flag u(1)  if( sps_poc_msb_flag )   poc_msb_len_minus1 ue(v)  num_extra_ph_bits_bytes u(2)   extra_ph_bits_struct( num_extra_ph_bits_bytes )  num_extra_sh_bits_bytes u(2)   extra_sh_bits_struct( num_extra_sh_bits_bytes )  if( sps_max_sublayers_minus1 > 0 )   sps_sublayer_dpb_params_flag u(1)  if( sps_ptl_dpb_hrd_params_present_flag )   dpb_parameters( sps_max_sublayers_minus1, sps_sublayer_dpb_params_flag )  long_term_ref_pics_flag u(1)  inter_layer_ref_pics_present_flag u(1)  sps_idr_rpl_present_flag u(1)  rpl1_same_as_rpl0_flag u(1)  for( i = 0; i < !rpl1_same_as_rpl0_flag ? 2 : 1; i++ ) {   num_ref_pic_lists_in_sps[ i ] ue(v)   for( j = 0; j < num_ref_pic_lists_in_sps[ i ]; j++)    ref_pic_list_struct( i, j )  }  if( ChromaArrayType != 0 )   qtbtt_dual_tree_intra_flag u(1)  log2_min_luma_coding_block_size_minus2 ue(v)  partition_constraints_override_enabled_flag u(1)  sps_log2_diff_min_qt_min_cb_intra_slice_luma ue(v)  sps_max_mtt_hierarchy_depth_intra_slice_luma ue(v)  if( sps_max_mtt_hierarchy_depth_intra_slice_luma != 0 ) {   sps_log2_diff_max_bt_min_qt_intra_slice_luma ue(v)   sps_log2_diff_max_tt_min_qt_intra_slice_luma ue(v)  }  sps_log2_diff_min_qt_min_cb_inter_slice ue(v)  sps_max_mtt_hierarchy_depth_inter_slice ue(v)  if( sps_max_mtt_hierarchy_depth_inter_slice != 0 ) {   sps_log2_diff_max_bt_min_qt_inter_slice ue(v)   sps_log2_diff_max_tt_min_qt_inter_slice ue(v)  }  if( qtbtt_dual_tree_intra_flag ) {   sps_log2_diff_min_qt_min_cb_intra_slice_chroma ue(v)   sps_max_mtt_hierarchy_depth_intra_slice_chroma ue(v)   if( sps_max_mtt_hierarchy_depth_intra_slice_chroma != 0 ) {    sps_log2_diff_max_bt_min_qt_intra_slice_chroma ue(v)    sps_log2_diff_max_tt_min_qt_intra_slice_chroma ue(v)   }  }  sps_max_luma_transform_size_64_flag u(1)  if( ChromaArrayType != 0 ) {   sps_joint_cbcr_enabled_flag u(1)   same_qp_table_for_chroma u(1)   numQpTables = same_qp_table_for_chroma ? 1 : ( sps_joint_cbcr_enabled_flag ? 3 : 2 )   for( i = 0; i < numQpTables; i++ ) {    qp_table_start_minus26[ i ] se(v)    num_points_in_qp_table_minus1[ i ] ue(v)    for( j = 0; j <= num_points_in_qp_table_minus1[ i ]; j++ ) {     delta_qp_in_val_minus1[ i ][ j ] ue(v)     delta_qp_diff_val[ i ][ j ] ue(v)    }   }  }  sps_sao_enabled_flag u(1)  sps_alf_enabled_flag u(1)  if( sps_alf_enabled_flag && ChromaArrayType != 0 )   sps_ccalf_enabled_flag u(1)  sps_transform_skip_enabled_flag u(1)  if( sps_transform_skip_enabled_flag ) {   log2_transform_skip_max_size_minus2 ue(v)   sps_bdpcm_enabled_flag u(1)  }  sps_ref_wraparound_enabled_flag u(1)  sps_temporal_mvp_enabled_flag u(1)  if( sps_temporal_mvp_enabled_flag )   sps_sbtmvp_enabled_flag u(1)  sps_amvr_enabled_flag u(1)  sps_bdof_enabled_flag u(1)  if( sps_bdof_enabled_flag )   sps_bdof_pic_present_flag u(1)  sps_smvd_enabled_flag u(1)  sps_dmvr_enabled_flag u(1)  if( sps_dmvr_enabled_flag)   sps_dmvr_pic_present_flag u(1)  sps_mmvd_enabled_flag u(1)  sps_isp_enabled_flag u(1)  sps_mrl_enabled_flag u(1)  sps_mip_enabled_flag u(1)  if( ChromaArrayType != 0 )   sps_cclm_enabled_flag u(1)  if( chroma_format_idc = = 1 ) {   sps_chroma_horizontal_collocated_flag u(1)   sps_chroma_vertical_collocated_flag u(1)  }  sps_mts_enabled_flag u(1)  if( sps_mts_enabled_flag ) {   sps_explicit_mts_intra_enabled_flag u(1)   sps_explicit_mts_inter_enabled_flag u(1)  }  six_minus_max_num_merge_cand ue(v)  sps_sbt_enabled_flag u(1)  sps_affine_enabled_flag u(1)  if( sps_affine_enabled_flag ) {   five_minus_max_num_subblock_merge_cand ue(v)   sps_affine_type_flag u(1)   if( sps_amvr_enabled_flag )    sps_affine_amvr_enabled_flag u(1)   sps_affine_prof_enabled_flag u(1)   if( sps_affine_prof_enabled_flag )    sps_prof_pic_present_flag u(1)  }  sps_palette_enabled_flag u(1)  if( ChromaArrayType = = 3 && !sps_max_luma_transform_size_64_flag )   sps_act_enabled_flag u(1)  if( sps_transform_skip_enabled_flag | | sps_palette_enabled_flag )   min_qp_prime_ts_minus4 ue(v)  sps_bcw_enabled_flag u(1)  sps_ibc_enabled_flag u(1)  if( sps_ibc_enabled_flag )   six_minus_max_num_ibc_merge_cand ue(v)  sps_ciip_enabled_flag u(1)  if( sps_mmvd_enabled_flag )   sps_fpel_mmvd_enabled_flag u(1)  if( MaxNumMergeCand >= 2 ) {   sps_gpm_enabled_flag u(1)   if( sps_gpm_enabled_flag && MaxNumMergeCand >= 3 )    max_num_merge_cand_minus_max_num_gpm_cand ue(v)  }  sps_lmcs_enabled_flag u(1)  sps_lfnst_enabled_flag u(1)  sps_ladf_enabled_flag u(1)  if( sps_ladf_enabled_flag ) {   sps_num_ladf_intervals_minus2 u(2)   sps_ladf_lowest_interval_qp_offset se(v)   for( i = 0; i < sps_num_ladf_intervals_minus2 + 1; i++ ) {    sps_ladf_qp_offset[ i ] se(v)    sps_ladf_delta_threshold_minus1[ i ] ue(v)   }  }  log2_parallel_merge_level_minus2 ue(v)  sps_scaling_list_enabled_flag u(1)  sps_dep_quant_enabled_flag u(1)  if( !sps_dep_quant_enabled flag )   sps_sign_data_hiding_enabled_flag u(1)  sps_virtual_boundaries_enabled_flag u(1)  if( sps_virtual_boundaries_enabled_flag ) {   sps_virtual_boundaries_present_flag u(1)   if( sps_virtual_boundaries_present_flag ) {    sps_num_ver_virtual_boundaries u(2)    for( i = 0; i < sps_num_ver_virtual_boundaries; i++ )     sps_virtual_boundaries_pos_x[ i ] u(13)    sps_num_hor_virtual_boundaries u(2)    for( i = 0; i < sps_num_hor_virtual_boundaries; i++ )     sps_virtual_boundaries_pos_y[ i ] u(13)   }  }  if( sps_ptl_dpb_hrd_params_present_flag ) {   sps_general_hrd_params_present_flag u(1)   if( sps_general_hrd_params_present_flag ) {    general_hrd_parameters( )    if( sps_max_sublayers_minus1 > 0 )     sps_sublayer_cpb_params_present_flag u(1)    firstSubLayer = sps_sublayer_cpb_params_present_flag ? 0 :      sps_max_sublayers_minus1    ols_hrd_parameters( firstSubLayer, sps_max_sublayers_minus1 )   }  }  field_seq_flag u(1)  vui_parameters_present_flag u(1)  if( vui_parameters_present flag )   vui_parameters( ) /* Specified in ITU-T H.SEI | ISO/IEC 23002-7 */  sps_extension_flag u(1)  if( sps_extension_flag )   while( more_rbsp_data( ) )    sps_extension_data_flag u(1)  rbsp_trailing_bits( ) }

With respect to Table 6, WET-Q2001 provides the following semantics:

-   An SPS RBSP shall be available to the decoding process prior to it     being referenced, included in at least one AU with TemporalId equal     to 0 or provided through external means. -   All SPS NAL units with a particular value of     sps_seq_parameter_set_id in a CVS shall have the same content. -   sps_seq_parameter_set_id provides an identifier for the SPS for     reference by other syntax elements. -   SPS NAL units, regardless of the nuh_layer_id values, share the same     value space of sps_seq_parameter_set_id. -   Let spsLayerId be the value of the nuh_layer_id of a particular SPS     NAL unit, and vclLayerId be the value of the nuh_layer_id of a     particular VCL NAL unit. The particular VCL NAL unit shall not refer     to the particular SPS NAL unit unless spsLayerId is less than or     equal to vclLayerId and the layer with nuh_layer_id equal to     spsLayerId is included in at least one OLS that includes the layer     with nuh_layer_id equal to vclLayerId.

sps_video_parameter_set_id, when greater than 0, specifies the value of vps_video_parameter_set_id for the VPS referred to by the SPS.

-   When sps_video_parameter_set_id is equal to 0, the following     applies:

The SPS does not refer to a VPS.

No VPS is referred to when decoding each CLVS referring to the SPS.

The value of vps_max_layers_minus1 is inferred to be equal to 0.

The CVS shall contain only one layer (i.e., all VCL NAL unit in the CVS shall have the same value of nuh_layer_id).

The value of GeneralLayerIdx[nuh_layer_id] is inferred to be equal to 0.

The value of vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is inferred to be equal to 1.

-   When vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is     equal to 1, the SPS referred to by a CLVS with a particluar     nuh_layer_id value nuhLayerId shall have nuh_layer_id equal to     nuhLayerId. -   The value of sps_video_parameter_set_id shall be the same in all     SPSs that are referred to by CLVSs in a CVS. -   sps_max_sublayers_minus1 plus 1 specifies the maximum number of     temporal sublayers that may be present in each CLVS referring to the     SPS. The value of sps_max_sublayers_minus1 shall be in the range of     0 to vps_max_sublayers_minus1, inclusive. -   sps_reserved_zero_4bits shall be equal to 0 in bitstreams conforming     to this version of this Specification. Other values for     sps_reserved_zero_4bits are reserved for future use by ITU-T |     ISO/IEC. -   sps_ptl_dpb_hrd_params_present_flag equal to 1 specifies that a     profile_tier_level( ) syntax structure and a dpb_parameters( )     syntax structure are present in the SPS, and a     general_hrd_parameters( ) syntax structure and an     ols_hrd_parameters( ) syntax structure may also be present in the     SPS. sps_ptl_dpb_hrd_params_present_flag equal to 0 specifies that     none of these four syntax structures is present in the SPS. The     value of sps_ptl_dpb_hrd_params_present_flag shall be equal to     vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]]. -   gdr_enabled_flag equal to 1 specifies that GDR pictures may be     present in CLVSs referring to the SPS. gdr_enabled_flag equal to 0     specifies that GDR pictures are not present in CLVSs referring to     the SPS. -   chroma_format_idc specifies the chroma sampling relative to the luma     sampling as specified. -   separate_colour_plane_flag equal to 1 specifies that the three     colour components of the 4:4:4 chroma format are coded separately.     separate_colour_plane_flag equal to 0 specifies that the colour     components are not coded separately. When separate_colour_plane_flag     is not present, it is inferred to be equal to 0. When     separate_colour_plane_flag is equal to 1, the coded picture consists     of three separate components, each of which consists of coded     samples of one colour plane (Y, Cb, or Cr) and uses the monochrome     coding syntax. In this case, each colour plane is associated with a     specific colour_plane_id value. -   NOTE—There is no dependency in decoding processes between the colour     planes having different colour_plane_id values. For example, the     decoding process of a monochrome picture with one value of     colour_plane_id does not use any data from monochrome pictures     having different values of colour_plane_id for inter prediction. -   Depending on the value of separate_colour_plane_flag, the value of     the variable ChromaArrayType is assigned as follows:

If separate_colour_plane_flag is equal to 0, ChromaArrayType is set equal to chroma_format_idc.

Otherwise (separate_colour_plane_flag is equal to 1), ChromaArrayType is set equal to 0.

-   res_change_in_clvs_allowed_flag equal to 1 specifies that the     picture spatial resolution may change within a CLVS referring to the     SPS. res_change_in_clvs_allowed_flag equal to 0 specifies that the     picture spatial resolution does not change within any CLVS referring     to the SPS. -   pic_width_max_in_luma_samples specifies the maximum width, in units     of luma samples, of each decoded picture referring to the SPS.     pic_width_max_in_luma_samples shall not be equal to 0 and shall be     an integer multiple of Max(8, MinCbSizeY). -   It is a requirement of bitstream conformance that, for any OLS with     OLS index i that contains one or more layers that refers to the SPS,     the value of pic_width_max_in_luma_samples shall be less than or     equal to the value of ols_dpb_pic_width[i]. -   pic_height_max_in_luma_samples specifies the maximum height, in     units of luma samples, of each decoded picture referring to the SPS.     pic_height_max_in_luma_samples shall not be equal to 0 and shall be     an integer multiple of Max(8, MinCbSizeY). -   It is a requirement of bitstream conformance that, for any OLS with     OLS index i that contains one or more layers that refers to the SPS,     the value of pic_height_max_in_luma_samples shall be less than or     equal to the value of ols_dpb_pic_height[i]. -   sps_conformance_window_flag equal to 1 indicates that the     conformance cropping window offset parameters follow next in the     SPS. sps_conformance_window_flag equal to 0 indicates that the     conformance cropping window offset parameters are not present in the     SPS. -   sps_conf_win_left_offset, sps_conf_win_right_offset,     sps_conf_win_top_offset, and sps_conf_win_bottom_offset specify the     cropping window that is applied to pictures with     pic_width_in_luma_samples equal to pic_width_max_in_luma_samples and     pic_height_in_luma_samples equal to pic_height_max_in_luma_samples.     When sps_conformance_window_flag is equal to 0, the values of     sps_conf_win_left_offset, sps_conf_win_right_offset,     sps_conf_win_top_offset, and sps_conf_win_bottom_offset are inferred     to be equal to 0. -   The conformance cropping window contains the luma samples with     horizontal picture coordinates from SubWidthC *     sps_conf_win_left_offset to     pic_width_max_in_luma_samples−(SubWidthC *     sps_conf_win_right_offset+1) and vertical picture coordinates from     SubHeightC * sps_conf_win_top_offset to     pic_height_max_in_luma_samples−(SubHeightC *     sps_conf_win_bottom_offset+1), inclusive. -   The value of SubWidthC *     (sps_conf_win_left_offset+sps_conf_win_right_offset) shall be less     than pic_width_max_in_luma_samples, and the value of SubHeightC *     (sps_conf_win_top_offset+sps_conf_win_bottom_offset) shall be less     than pic_height_max_in_luma_samples. -   When ChromaArrayType is not equal to 0, the corresponding specified     samples of the two chroma arrays are the samples having picture     coordinates (x/SubWidthC, y/SubHeightC), where (x, y) are the     picture coordinates of the specified luma samples. -   NOTE—The conformance cropping window offset parameters are only     applied at the output. All internal decoding processes are applied     to the uncropped picture size. -   sps_log2_ctu_size_minus5 plus 5 specifies the luma coding tree block     size of each CTU. The value of sps_log2_ctu_size_minus5 shall be in     the range of 0 to 2, inclusive. The value 3 for     sps_log2_ctu_size_minus5 is reserved for future use by ITU-T     ISO/IEC. -   The variables CtbLog2SizeY and CtbSizeY are derived as follows: -   CtbLog2SizeY=sps_log2_ctu_size_minus5+5 -   CtbSizeY=1<<CtbLog2SizeY -   subpic_info_present_flag equal to 1 specifies that subpicture     information is present for the CLVS and there may be one or more     than one subpicture in each picture of the CLVS.     subpic_info_present_flag equal to 0 specifies that subpicture     information is not present for the CLVS and there is only one     subpicture in each picture of the CLVS. -   When res_change_in_clvs_allowed_flag is equal to 1, the value of     subpic_info_present_flag shall be equal to 0. -   NOTE—When a bitstream is the result of a sub-bitstream extraction     process and contains only a subset of the subpictures of the input     bitstream to the sub-bitstream extraction process, it might be     required to set the value of subpic_info_present_flag equal to 1 in     the RBSP of the SPSs. -   sps_num_subpics_minus1 plus 1 specifies the number of subpictures in     each picture in the CLVS. The value of sps_num_subpics_minus1 shall     be in the range of 0 to     Ceil(pic_width_max_in_luma_samples÷CtbSizeY) *     Ceil(pic_height_max_in_luma_samples÷CtbSizeY)−1, inclusive. When not     present, the value of sps_num_subpics_minus1 is inferred to be equal     to 0. -   sps_independent_subpics_flag equal to 1 specifies that no intra     prediction, no inter prediction and no in-loop filtering operations     may be performed across any subpicture boundary in the CLVS.     sps_independent_subpics_flag equal to 0 specifies that inter     prediction or in-loop filtering operations across the subpicture     boundaries in the CLVS may be allowed. When not present, the value     of sps_independent_subpics_flag is inferred to be equal to 0. -   subpic_ctu_top_left_x[i] specifies horizontal position of top left     CTU of i-th subpicture in unit of CtbSizeY. The length of the syntax     element is Ceil(Log2((pic_width_max_in_luma     samples+CtbSizeY−1) >>CtbLog2SizeY)) bits. When not present, the     value of subpic_ctu_top_left_x[i] is inferred to be equal to 0. -   subpic_ctu_top_left_y[i] specifies vertical position of top left CTU     of i-th subpicture in unit of CtbSizeY. The length of the syntax     element is     Ceil(Log2((pic_height_max_in_luma_samples+CtbSizeY−1) >>CtbLog2SizeY))     bits. When not present, the value of subpic_ctu_top_left_y[i] is     inferred to be equal to 0. -   subpic_width_minus1[i] plus 1 specifies the width of the i-th     subpicture in units of CtbSizeY. The length of the syntax element is     Ceil(Log2((pic_width_max_in_luma_samples+CtbSizeY−1) >>CtbLog2SizeY))     bits. When not present, the value of subpic_width_minus1[i] is     inferred to be equal to     ((pic_width_max_in_luma_samples+CtbSizeY−1) >>CtbLog2SizeY)−subpic_ctu_top_le     ft_x[ i]−1. -   subpic_height_minus1[i] plus 1 specifies the height of the i-th     subpicture in units of CtbSizeY. The length of the syntax element is     Ceil(Log2((pic_height_max_in_luma_samples+CtbSizeY−1) >>CtbLog2SizeY))     bits. When not present, the value of subpic_height_minus1[i] is     inferred to be equal to     ((pic_height_max_in_luma_samples+CtbSizeY−1) >>CtbLog2SizeY)−subpic_ctu_top_le     ft_y[i]−1. -   subpic_treated_as_pic_flag[i] equal to 1 specifies that the i-th     subpicture of each coded picture in the CLVS is treated as a picture     in the decoding process excluding in-loop filtering operations.     subpic_treated_as_pic_flag[i] equal to 0 specifies that the i-th     subpicture of each coded picture in the CLVS is not treated as a     picture in the decoding process excluding in-loop filtering     operations. When not present, the value of     subpic_treated_as_pic_flag[i] is inferred to be equal to     sps_independent_subpics_flag. -   When subpic_treated_as_pic_flag[i] is equal to 1, it is a     requirement of bitstream conformance that all of the following     conditions are true true for each output layer and its reference     layers in an OLS that includes the layer containing the i-th     subpicture as an output layer:

All pictures in the output layer and its reference layers shall have the same value of pic_width_in_luma_samples and the same value of pic_height_in_luma_samples.

All the SPSs referred to by the output layer and its reference layers shall have the same value of sps_num_subpics_minus1 and shall have the same values of subpic_ctu_top_left_x[j ], subpic_ctu_top_left_y[j], subpic_width_minus1[j], subpic_height_minus1[j], and loop_filter_across_subpic_enabled_flag[j], respectively, for each value of j in the range of 0 to sps_num_subpics_minus1, inclusive.

All pictures in each access unit in the output layer and its reference layers shall have the same value of SubpicIdVal[j] for each value of j in the range of 0 to sps_num_subpics_minus1, inclusive.

-   loop_filter_across_subpic_enabled_flag[i] equal to 1 specifies that     in-loop filtering operations may be performed across the boundaries     of the i-th subpicture in each coded picture in the CLVS.     loop_filter_across_subpic_enabled_flag[i] equal to 0 specifies that     in-loop filtering operations are not performed across the boundaries     of the i-th subpicture in each coded picture in the CLVS. When not     present, the value of loop_filter_across_subpic_enabled_pic_flag[i]     is inferred to be equal to 1−sps_independent_subpics_flag. -   It is a requirement of bitstream conformance that the shapes of the     subpictures shall be such that each subpicture, when decoded, shall     have its entire left boundary and entire top boundary consisting of     picture boundaries or consisting of boundaries of previously decoded     subpictures. -   sps_subpic_id_len_minus1 plus 1 specifies the number of bits used to     represent the syntax element sps_subpic_id[i], the syntax elements     pps_subpic_id[i], when present, and the syntax element     slice_subpic_id, when present. The value of sps_subpic_id_len_minus1     shall be in the range of 0 to 15, inclusive. The value of 1     <<(sps_subpic_id_len_minus1+1) shall be greater than or equal to     sps_num_subpics_minus1+1. -   subpic_id_mapping_explicitly_signalled_flag equal to 1 specifies     that the subpicture ID mapping is explicitly signalled, either in     the SPS or in the PPSs referred to by coded pictures of the CLVS.     subpic_id_mapping_explicitly_signalled_flag equal to 0 specifies     that the subpicture ID mapping is not explicitly signalled for the     CLVS. When not present, the value of     subpic_id_mapping_explicitly_signalled_flag is inferred to be equal     to 0. -   subpic_id_mapping_in_sps_flag equal to 1 specifies that the     subpicture ID mapping is signalled in the SPS when     subpic_id_mapping_explicitly_signalled_flag is equal to 1.     subpic_id_mapping_in_sps_flag equal to 0 specifies that subpicture     ID mapping is signalled in the PPSs referred to by coded pictures of     the CLVS when subpic_id_mapping_explicitly_signalled_flag is equal     to 1. -   sps_subpic_id[i] specifies the subpicture ID of the i-th subpicture.     The length of the sps_subpic_id[i] syntax element is     sps_subpic_id_len_minus1+1 bits. -   bit_depth_minus8 specifies the bit depth of the samples of the luma     and chroma arrays, BitDepth, and the value of the luma and chroma     quantization parameter range offset, QpBdOffset, as follows: -   BitDepth=8+bit_depth_minus8 -   QpBdOffset=6 * bit_depth_minus8 -   bit_depth_minus8 shall be in the range of 0 to 8, inclusive. -   sps_entropy_coding_sync_enabled_flag equal to 1 specifies that a     specific synchronization process for context variables is invoked     before decoding the CTU that includes the first CTB of a row of CTBs     in each tile in each picture referring to the SPS, and a specific     storage process for context variables is invoked after decoding the     CTU that includes the first CTB of a row of CTBs in each tile in     each picture referring to the SPS.     sps_entropy_coding_sync_enabled_flag equal to 0 specifies that no     specific synchronization process for context variables is required     to be invoked before decoding the CTU that includes the first CTB of     a row of CTBs in each tile in each picture referring to the SPS, and     no specific storage process for context variables is required to be     invoked after decoding the CTU that includes the first CTB of a row     of CTBs in each tile in each picture referring to the SPS. -   sps_wpp_entry_point_offsets_present_flag equal to 1 specifies that     signalling for entry point offsets for CTU rows may be present in     the slice headers of pictures referring to the SPS when     sps_entropy_coding_sync_enabled_flag is equal to 1.     sps_wpp_entry_point_offsets_present_flag equal to 0 specifies that     signalling for entry point offsets for CTU rows are not present in     the slice headers of pictures referring to the SPS. When not     present, the value of sps_wpp_entry_point_offsets_present_flag is     inferred to be equal to 0. -   sps_weighted_pred_flag equal to 1 specifies that weighted prediction     may be applied to P slices referring to the SPS.     sps_weighted_pred_flag equal to 0 specifies that weighted prediction     is not applied to P slices referring to the SPS. -   sps_weighted_bipred_flag equal to 1 specifies that explicit weighted     prediction may be applied to B slices referring to the SPS.     sps_weighted_bipred_flag equal to 0 specifies that explicit weighted     prediction is not applied to B slices referring to the SPS. -   log2_max_pic_order_cnt_lsb_minus4 specifies the value of the     variable MaxPicOrderCntLsb that is used in the decoding process for     picture order count as follows: -   MaxPicOrderCntLsb=2^((log2_max_pic_order_cnt_lsb_minus4+4)) -   The value of log2_max_pic_order_cnt_lsb_minus4 shall be in the range     of 0 to 12, inclusive. -   sps_poc_msb_flag equal to 1 specifies that the     ph_poc_msb_present_flag syntax element is present in PHs referring     to the SPS. sps_poc_msb_flag equal to 0 specifies that the     ph_poc_msb_present_flag syntax element is not present in PHs     referring to the SPS. -   poc_msb_len_minus1 plus 1 specifies the length, in bits, of the     poc_msb_val syntax elements, when present in the PHs referring to     the SPS. The value of poc_msb_len_minus1 shall be in the range of 0     to 32−log2_max_pic_order_cnt_lsb_minus4−5, inclusive. -   num_extra_ph_bits_bytes specifies the number of bytes of extra bits     in the PH syntax structure for coded pictures referring to the SPS.     The value of num_extra_ph_bits_bytes shall be equal to 0 in     bitstreams conforming to this version of this Specification.     Although the value of num_extra_ph_bits_bytes is required to be     equal to 0 in this version of this Specification, decoder conforming     to this version of this Specification shall allow the value of     num_extra_ph_bits_bytes equal to 1 or 2 to appear in the syntax. -   num_extra_sh_bits_bytes specifies the number of bytes of extra bits     in the slice headers for coded pictures referring to the SPS. The     value of num_extra_sh_bits_bytes shall be equal to 0 in bitstreams     conforming to this version of this Specification. Although the value     of num_extra_sh_bits_bytes is required to be equal to 0 in this     version of this Specification, decoder conforming to this version of     this Specification shall allow the value of num_extra_sh_bits_bytes     equal to 1 or 2 to appear in the syntax. -   sps_sublayer_dpb_params_flag is used to control the presence of     max_dec_pic_buffering_minus1[i], max_num_reorder_pics[i], and     max_latency_increase_plus1[i] syntax elements in the dpb_parameters(     ) syntax strucure in the SPS. When not present, the value of     sps_sub_dpb_params_info_present_flag is inferred to be equal to 0. -   long_term_ref_pics_flag equal to 0 specifies that no LTRP is used     for inter prediction of any coded picture in the CLVS.     long_term_ref_pics_flag equal to 1 specifies that LTRPs may be used     for inter prediction of one or more coded pictures in the CLVS. -   inter_layer_ref_pics_present_flag equal to 0 specifies that no ILRP     is used for inter prediction of any coded picture in the CLVS.     inter_layer_ref_pic_flag equal to 1 specifies that ILRPs may be used     for inter prediction of one or more coded pictures in the CLVS. When     sps_video_parameter_set_id is equal to 0, the value of     inter_layer_ref_pics_present_flag is inferred to be equal to 0. When     vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is equal     to 1, the value of inter_layer_ref_pics_present_flag shall be equal     to 0. -   sps_idr_rpl_present_flag equal to 1 specifies that reference picture     list syntax elements are present in slice headers of IDR pictures.     sps_idr_rpl_present_flag equal to 0 specifies that reference picture     list syntax elements are not present in slice headers of IDR     pictures. -   rpl1_same_as_rpl0_flag equal to 1 specifies that the syntax element     num_ref_pic_lists_in_sps[1] and the syntax structure     ref_pic_list_struct(1, rplsIdx) are not present and the following     applies:

The value of num_ref_pic_lists_in_sps[1] is inferred to be equal to the value of num_ref_pic_lists_in_sps[0].

The value of each of syntax elements in ref_pic_list_struct(1, rplsIdx) is inferred to be equal to the value of corresponding syntax element in ref_pic_list_struct(0, rplsIdx) for rplsIdx ranging from 0 to num_ref_pic_lists_in_sps[0]−1.

-   num_ref_pic_lists_in_sps[i] specifies the number of the     ref_pic_list_struct(listIdx, rplsIdx) syntax structures with listIdx     equal to i included in the SPS. The value of     num_ref_pic_lists_in_sps[i] shall be in the range of 0 to 64,     inclusive. -   NOTE—For each value of listIdx (equal to 0 or 1), a decoder should     allocate memory for a total number of num_ref_pic_lists_in_sps[i]+1     ref_pic_list_struct(listIdx, rplsIdx) syntax structures since there     may be one ref_pic_list_struct(listIdx, rplsIdx) syntax structure     directly signalled in the slice headers of a current picture. -   qtbtt_dual_tree_intra_flag equal to 1 specifies that, for I slices,     each CTU is split into coding units with 64×64 luma samples using an     implicit quadtree split, and these coding units are the root of two     separate coding_tree syntax structure for luma and chroma.     qtbtt_dual_tree_intra_flag equal to 0 specifies separate coding_tree     syntax structure is not used for I slices. When     qtbtt_dual_tree_intra_flag is not present, it is inferred to be     equal to 0. -   log2_min_luma_coding_block_size_minus2 plus 2 specifies the minimum     luma coding block size. The value range of     log2_min_luma_coding_block_size_minus2 shall be in the range of 0 to     Min(4, sps_log2_ctu_size_minus5+3), inclusive. -   The variables MinCbLog2SizeY, MinCbSizeY, IbcBufWidthY, IbcBufWidthC     and Vsize are derived as follows: -   MinCbLog2SizeY=log2_min_luma_coding_block_size_minus2+2 -   MinCbSizeY=1<<MinCbLog2SizeY -   IbcBufWidthY=256 * 128/CtbSizeY -   IbcBufWidthC=IbcBufWidthY/SubWidthC -   VSize=Min(64, CtbSizeY) -   The value of MinCbSizeY shall less than or equal to VSize. -   The variables CtbWidthC and CtbHeightC, which specify the width and     height, respectively, of the array for each chroma CTB, are derived     as follows:

If chroma_format_idc is equal to 0 (monochrome) or separate_colour_plane_flag is equal to 1, CtbWidthC and CtbHeightC are both equal to 0.

Otherwise, CtbWidthC and CtbHeightC are derived as follows:

-   CtbWidthC=CtbSizeY/SubWidthC -   CtbHeightC=Ctb SizeY/SubHeightC -   For log2BlockWidth ranging from 0 to 4 and for log2BlockHeight     ranging from 0 to 4, inclusive, the up-right diagonal scan order     array initialization process as specified is invoked with     1<<log2BlockWidth and 1<<log2BlockHeight as inputs, and the output     is assigned to DiagScanOrder[log2BlockWidth][log2BlockHeight]. -   For log2BlockWidth ranging from 0 to 6 and for log2BlockHeight     ranging from 0 to 6, inclusive, the horizontal and vertical traverse     scan order array initialization process as specified is invoked with     1<<log2BlockWidth and 1<<log2BlockHeight as inputs, and the output     is assigned to HorTravScanOrder[log2BlockWidth][log2BlockHeight] and     VerTravScanOrder[log2BlockWidth][log2BlockHeight]. -   partition_constraints_override_enabled_flag equal to 1 specifies the     presence of partition_constraints_override_flag in PHs referring to     the SPS. partition_constraints_override_enabled_flag equal to 0     specifies the absence of partition_constraints_override_flag in PHs     referring to the SPS. -   sps_log2_diff_min_qt_min_cb_intra_slice_luma specifies the default     difference between the base 2 logarithm of the minimum size in luma     samples of a luma leaf block resulting from quadtree splitting of a     CTU and the base 2 logarithm of the minimum coding block size in     luma samples for luma CUs in slices with slice type equal to 2 (I)     referring to the SPS. When     partition_constraints_override_enabled_flag is equal to 1, the     default difference can be overridden by     ph_log2_diff_min_qt_min_cb_luma present in PHs referring to the SPS.     The value of sps_log2_diff_min_qt_min_cb_intra_slice_luma shall be     in the range of 0 to CtbLog2SizeY−MinCbLog2SizeY, inclusive. The     base 2 logarithm of the minimum size in luma samples of a luma leaf     block resulting from quadtree splitting of a CTU is derived as     follows: -   MinQtLog2SizeIntraY=sps_log2_diff_min_qt_min_cb_intra_slice_luma+MinCbLog2SizeY -   sps_max_mtt_hierarchy_depth_intra_slice_luma specifies the default     maximum hierarchy depth for coding units resulting from multi-type     tree splitting of a quadtree leaf in slices with slice_type equal to     2 (I) referring to the SPS. When     partition_constraints_override_enabled_flag is equal to 1, the     default maximum hierarchy depth can be overridden by     ph_max_mtt_hierarchy_depth_intra_slice_luma present in PHs referring     to the SPS. The value of     sps_max_mtt_hierarchy_depth_intra_slice_luma shall be in the range     of 0 to 2*(CtbLog2SizeY−MinCbLog2SizeY), inclusive. -   sps_log2_diff_max_bt_min_qt_intra_slice_luma specifies the default     difference between the base 2 logarithm of the maximum size (width     or height) in luma samples of a luma coding block that can be split     using a binary split and the minimum size (width or height) in luma     samples of a luma leaf block resulting from quadtree splitting of a     CTU in slices with slice_type equal to 2 (I) referring to the SPS.     When partition_constraints_override_enabled_flag is equal to 1, the     default difference can be overridden by     ph_log2_diff_max_bt_min_qt_luma present in PHs referring to the SPS.     The value of sps_log2_diff_max_bt_min_qt_intra_slice_luma shall be     in the range of 0 to CtbLog2SizeY−MinQtLog2SizeIntraY, inclusive.     When sps_log2_diff_max_bt_min_qt_intra_slice_luma is not present,     the value of sps_log2_diff_max_bt_min_qt_intra_slice_luma is     inferred to be equal to 0. -   sps_log2_diff_max_tt_min_qt_intra_slice_luma specifies the default     difference between the base 2 logarithm of the maximum size (width     or height) in luma samples of a luma coding block that can be split     using a ternary split and the minimum size (width or height) in luma     samples of a luma leaf block resulting from quadtree splitting of a     CTU in slices with slice_type equal to 2 (I) referring to the SPS.     When partition_constraints_override_enabled_flag is equal to 1, the     default difference can be overridden by     ph_log2_diff_max_tt_min_qt_luma present in PHs referring to the SPS.     The value of sps_log2_diff_max_tt_min_qt_intra_slice_luma shall be     in the range of 0 to CtbLog2SizeY−MinQtLog2SizeIntraY, inclusive.     When sps_log2_diff_max_tt_min_qt_intra_slice_luma is not present,     the value of sps_log2_diff_max_tt_min_qt_intra_slice_luma is     inferred to be equal to 0. -   sps_log2_diff_min_qt_min_cb_inter_slice specifies the default     difference between the base 2 logarithm of the minimum size in luma     samples of a luma leaf block resulting from quadtree splitting of a     CTU and the base 2 logarithm of the minimum luma coding block size     in luma samples for luma CUs in slices with slice_type equal to     0 (B) or 1 (P) referring to the SPS. When     partition_constraints_override_enabled_flag is equal to 1, the     default difference can be overridden by     ph_log2_diff_min_qt_min_cb_luma present in PHs referring to the SPS.     The value of sps_log2_diff_min_qt_min_cb_inter_slice shall be in the     range of 0 to CtbLog2SizeY−MinCbLog2SizeY, inclusive. The base 2     logarithm of the minimum size in luma samples of a luma leaf block     resulting from quadtree splitting of a CTU is derived as follows: -   MinQtLog2SizeInterY=sps_log2_diff_min_qt_min_cb     inter_slice+MinCbLog2SizeY -   sps_max_mtt_hierarchy_depth_inter_slice specifies the default     maximum hierarchy depth for coding units resulting from multi-type     tree splitting of a quadtree leaf in slices with slice_type equal to     0 (B) or 1 (P) referring to the SPS. When     partition_constraints_override_enabled_flag is equal to 1, the     default maximum hierarchy depth can be overridden by     ph_max_mtt_hierarchy_depth_inter_slice present in PHs referring to     the SPS. The value of sps_max_mtt_hierarchy_depth_inter_slice shall     be in the range of 0 to 2*(CtbLog2SizeY−MinCbLog2SizeY), inclusive. -   sps_log2_diff_max_bt_min_qt_inter_slice specifies the default     difference between the base 2 logarithm of the maximum size (width     or height) in luma samples of a luma coding block that can be split     using a binary split and the minimum size (width or height) in luma     samples of a luma leaf block resulting from quadtree splitting of a     CTU in slices with slice type equal to 0 (B) or 1 (P) referring to     the SPS. When partition_constraints_override_enabled_flag is equal     to 1, the default difference can be overridden by     ph_log2_diff_max_bt_min_qt_luma present in PHs referring to the SPS.     The value of sps_log2_diff_max_bt_min_qt_inter_slice shall be in the     range of 0 to CtbLog2SizeY−MinQtLog2SizeInterY, inclusive. When     sps_log2_diff_max_bt_min_qt_inter_slice is not present, the value of     sps_log2_diff_max_bt_min_qt_inter_slice is inferred to be equal to     0. -   sps_log2_diff_max_tt_min_qt_inter_slice specifies the default     difference between the base 2 logarithm of the maximum size (width     or height) in luma samples of a luma coding block that can be split     using a ternary split and the minimum size (width or height) in luma     samples of a luma leaf block resulting from quadtree splitting of a     CTU in slices with slice type equal to 0 (B) or 1 (P) referring to     the SPS. When partition_constraints_override_enabled_flag is equal     to 1, the default difference can be overridden by     ph_log2_diff_max_tt_min_qt_luma present in PHs referring to the SPS.     The value of sps_log2_diff_max_tt_min_qt_inter_slice shall be in the     range of 0 to CtbLog2SizeY−MinQtLog2SizeInterY, inclusive. When     sps_log2_diff_max_tt_min_qt_inter_slice is not present, the value of     sps_log2_diff_max_tt_min_qt_inter_slice is inferred to be equal to     0. -   sps_log2_diff_min_qt_min_cb_intra_slice_chroma specifies the default     difference between the base 2 logarithm of the minimum size in luma     samples of a chroma leaf block resulting from quadtree splitting of     a chroma CTU with treeType equal to DUAL_TREE_CHROMA and the base 2     logarithm of the minimum coding block size in luma samples for     chroma CUs with treeType equal to DUAL_TREE_CHROMA in slices with     slice_type equal to 2 (I) referring to the SPS. When     partition_constraints_override_enabled_flag is equal to 1, the     default difference can be overridden by     ph_log2_diff_min_qt_min_cb_chroma present in PHs referring to the     SPS. The value of sps_log2_diff_min_qt_min_cb_intra_slice_chroma     shall be in the range of 0 to CtbLog2SizeY−MinCbLog2SizeY,     inclusive. When not present, the value of     sps_log2_diff_min_qt_min_cb_intra_slice_chroma is inferred to be     equal to 0. The base 2 logarithm of the minimum size in luma samples     of a chroma leaf block resulting from quadtree splitting of a CTU     with treeType equal to DUAL_TREE_CHROMA is derived as follows: -   MinQtLog2SizeIntraC=sps_log2_diff_min_qt_min_cb_intra_slice_chroma+MinCbLog2SizeY -   sps_max_mtt_hierarchy_depth_intra_slice_chroma specifies the default     maximum hierarchy depth for chroma coding units resulting from     multi-type tree splitting of a chroma quadtree leaf with treeType     equal to DUAL_TREE_CHROMA in slices with slice_type equal to 2 (I)     referring to the SPS. When     partition_constraints_override_enabled_flag is equal to 1, the     default maximum hierarchy depth can be overridden by     ph_max_mtt_hierarchy_depth_chroma present in PHs referring to the     SPS. The value of sps_max_mtt_hierarchy_depth_intra_slice_chroma     shall be in the range of 0 to 2*(CtbLog2SizeY−MinCbLog2SizeY),     inclusive. When not present, the value of     sps_max_mtt_hierarchy_depth_intra_slice_chroma is inferred to be     equal to 0. -   sps_log2_diff_max_bt_min_qt_intra_slice_chroma specifies the default     difference between the base 2 logarithm of the maximum size (width     or height) in luma samples of a chroma coding block that can be     split using a binary split and the minimum size (width or height) in     luma samples of a chroma leaf block resulting from quadtree     splitting of a chroma CTU with treeType equal to DUAL_TREE_CHROMA in     slices with slice_type equal to 2 (I) referring to the SPS. When     partition_constraints_override_enabled_flag is equal to 1, the     default difference can be overridden by     ph_log2_diff_max_bt_min_qt_chroma present in PHs referring to the     SPS. The value of sps_log2_diff_max_bt_min_qt_intra_slice_chroma     shall be in the range of 0 to CtbLog2SizeY−MinQtLog2SizeIntraC,     inclusive. When sps_log2_diff_max_bt_min_qt_intra_slice_chroma is     not present, the value of     sps_log2_diff_max_bt_min_qt_intra_slice_chroma is inferred to be     equal to 0. -   sps_log2_diff_max_tt_min_qt_intra_slice_chroma specifies the default     difference between the base 2 logarithm of the maximum size (width     or height) in luma samples of a chroma coding block that can be     split using a ternary split and the minimum size (width or height)     in luma samples of a chroma leaf block resulting from quadtree     splitting of a chroma CTU with treeType equal to DUAL_TREE_CHROMA in     slices with slice_type equal to 2 (I) referring to the SPS. When     partition_constraints_override_enabled_flag is equal to 1, the     default difference can be overridden by     ph_log2_diff_max_tt_min_qt_chroma present in PHs referring to the     SPS. The value of sps_log2_diff_max_tt_min_qt_intra_slice_chroma     shall be in the range of 0 to CtbLog2SizeY−MinQtLog2SizeIntraC,     inclusive. When sps_log2_diff_max_tt_min_qt_intra_slice_chroma is     not present, the value of     sps_log2_diff_max_tt_min_qt_intra_slice_chroma is inferred to be     equal to 0. -   sps_max_luma_transform_size_64_flag equal to 1 specifies that the     maximum transform size in luma samples is equal to 64.     sps_max_luma_transform_size_64_flag equal to 0 specifies that the     maximum transform size in luma samples is equal to 32. -   When CtbSizeY is less than 64, the value of     sps_max_luma_transform_size_64_flag shall be equal to 0. -   The variables MinTbLog2SizeY, MaxTbLog2SizeY, MinTbSizeY, and     MaxTbSizeY are derived as follows:

MinTbLog2SizeY = 2 MaxTbLog2SizeY = sps_max_luma_transform_size_64_flag ? 6 : 5 MinTbSizeY = 1 << MinTbLog2SizeY ) MaxTbSizeY = 1 << MaxTbLog2SizeY )

-   sps_joint_cbcr_enabled_flag equal to 0 specifies that the joint     coding of chroma residuals is disabled. sps_joint_cbcr_enabled_flag     equal to 1 specifies that the joint coding of chroma residuals is     enabled. When not present, the value of sps_joint_cbcr_enabled_flag     is inferred to be equal to 0. -   same_qp_table_for_chroma equal to 1 specifies that only one chroma     QP mapping table is signalled and this table applies to Cb and Cr     residuals and additionally to joint Cb-Cr residuals when     sps_joint_cbcr_enabled_flag is equal to 1. same_qp_table_for_chroma     equal to 0 specifies that chroma QP mapping tables, two for Cb and     Cr, and one additional for joint Cb-Cr when     sps_joint_cbcr_enabled_flag is equal to 1, are signalled in the SPS.     When same_qp_table_for_chroma is not present in the bitstream, the     value of same_qp_table_for_chroma is inferred to be equal to 1. -   qp_table_start_minus26[i] plus 26 specifies the starting luma and     chroma QP used to describe the i-th chroma QP mapping table. The     value of qp_table_start_minus26[i] shall be in the range of     −26−QpBdOffset to 36 inclusive. When qp_table_start_minus2[i] is not     present in the bitstream, the value of qp_table_start_minus26[i] is     inferred to be equal to 0. -   num_points_in_qp_table_minus1[i] plus 1 specifies the number of     points used to describe the i-th chroma QP mapping table. The value     of num_points_in_qp_table_minus1[i] shall be in the range of 0 to     63+QpBdOffset, inclusive. When num_points_in_qp_table_minus1[0] is     not present in the bitstream, the value of     num_points_in_qp_table_minus1[0] is inferred to be equal to 0. -   delta_qp_in_val_minus1[i][j] specifies a delta value used to derive     the input coordinate of the j-th pivot point of the i-th chroma QP     mapping table. When delta_qp_in_val_minus1[0][j] is not present in     the bitstream, the value of delta_qp_in_val_minus1[0][j] is inferred     to be equal to 0. -   delta_qp_diff_val[i][j] specifies a delta value used to derive the     output coordinate of the j-th pivot point of the i-th chroma QP     mapping table. -   The i-th chroma QP mapping table ChromaQpTable[i] for i=0.     numQpTables−1 is derived as follows:

qpInVal[ i ][ 0 ] = qp_table_start_minus26[ i ] + 26 qpOutVal[ i ][ 0 ] = qpInVal[ i ][ 0 ] for( j = 0; j <= num_points_in_qp_table_minus1[ i ]; j++ ) {  qpInVal[ i ][ j + 1 ] = qpInVal[ i ][ j ] + delta_qp_in_val_minus1[ i ][ j ] + 1  qpOutVal[ i ][ j + 1 ] = qpOutVal[ i ][ j ] + ( delta_qp_in_val_minus1[ i ][ j ] A delta_qp_diff_val[ i ][ j ] ) } ChromaQpTable[ i ][ qpInVal[ i ][ 0 ] ] = qpOutVal[ i ][ 0 ] for( k = qpInVal[ i ][ 0 ] − 1; k >= −QpBdOffset; k − − )  ChromaQpTable[ i ][ k ] = Clip3( −QpBdOffset, 63, ChromaQpTable[ i ][ k + 1 ] − 1 ) for( j = 0; j <= num_points_in_qp_table_minus1[ i ]; j++ ) {  sh = ( delta_qp_in_val_minus1[ i][j ] + 1) >> 1  for( k = qpInVal[ i ][ j ] + 1, m = 1; k <= qpInval[ i ][ j + 1 ]; k++, m++ )   ChromaQpTable[ i ][ k ] = ChromaQpTable[ i ][ qpInVal[ i ][ j ] ] +   ( ( qpOutVal[ i ][j + 1] − qpOutVal[ i ][j ] ) * m + sh )/ ( delta_qp_in_val_minus1[ i ][j] + 1 ) } for( k = qpInVal[ i ][ num_points_in_qp_table_minus1[ i ] + 1 ] + 1; k <= 63; k++ )  ChromaQpTable[ i ][ k ] = Clip3( −QpBdOffset, 63, ChromaQpTable[ i ][ k − 1 ] + 1 )

-   When same_qp_table_for_chroma is equal to 1, ChromaQpTable[1][k] and -   ChromaQpTable[2][k] are set equal to ChromaQpTable[0][k] for k in     the range of −QpBdOffset to 63, inclusive. -   It is a requirement of bitstream conformance that the values of     qpInVal[i][j] and qpOutVal[i][j] shall be in the range of     −QpBdOffset to 63, inclusive for i in the range of 0 to numQpTables     −1, inclusive, and j in the range of 0 to     num_points_in_qp_table_minus1[i]+1, inclusive. -   sps_sao_enabled_flag equal to 1 specifies that the sample adaptive     offset process is applied to the reconstructed picture after the     deblocking filter process. sps_sao_enabled_flag equal to 0 specifies     that the sample adaptive offset process is not applied to the     reconstructed picture after the deblocking filter process. -   sps_alf_enabled_flag equal to 0 specifies that the adaptive loop     filter is disabled. sps_alf_enabled_flag equal to 1 specifies that     the adaptive loop filter is enabled. -   sps_ccalf_enabled_flag equal to 0 specifies that the cross-component     adaptive loop filter is disabled. sps_ccalf_enabled_flag equal to 1     specifies that the cross-component adaptive loop filter may be     enabled. -   sps_transform_skip_enabled_flag equal to 1 specifies that     transform_skip_flag may be present in the transform unit syntax.     sps_transform_skip_enabled_flag equal to 0 specifies that     transform_skip_flag is not present in the transform unit syntax. -   log2_transform_skip_max_size_minus2 specifies the maximum block size     used for transform skip, and shall be in the range of 0 to 3,     inclusive. -   The variable MaxTsSize is set equal to     1<<(log2_transform_skip_max_size_minus2+2). -   sps_bdpcm_enabled_flag equal to 1 specifies that     intra_bdpcm_luma_flag and intra_bdpcm_chroma_flag may be present in     the coding unit syntax for intra coding units.     sps_bdpcm_enabled_flag equal to 0 specifies that     intra_bdpcm_luma_flag and intra_bdpcm_chroma_flag are not present in     the coding unit syntax for intra coding units. When not present, the     value of sps_bdpcm_enabled_flag is inferred to be equal to 0. -   sps_ref_wraparound_enabled_flag equal to 1 specifies that horizontal     wrap-around motion compensation is applied in inter prediction.     sps_ref_wraparound_enabled_flag equal to 0 specifies that horizontal     wrap-around motion compensation is not applied. When the value of     (CtbSizeY / MinCbSizeY+1) is greater than     (pic_width_in_luma_samples/MinCbSizeY−1), where     pic_width_in_luma_samples is the value of pic_width_in_luma_samples     in any PPS that refers to the SPS, the value of     sps_ref_wraparound_enabled_flag shall be equal to 0. -   sps_temporal_mvp_enabled_flag equal to 1 specifies that temporal     motion vector predictors may be used in the CLVS.     sps_temporal_mvp_enabled_flag equal to 0 specifies that temporal     motion vector predictors are not used in the CLVS. -   sps_sbtmvp_enabled_flag equal to 1 specifies that subblock-based     temporal motion vector predictors may be used in decoding of     pictures with all slices having slice_type not equal to I in the     CLVS. sps_sbtmvp_enabled_flag equal to 0 specifies that     subblock-based temporal motion vector predictors are not used in the     CLVS. When sps_sbtmvp_enabled_flag is not present, it is inferred to     be equal to 0. -   sps_amvr_enabled_flag equal to 1 specifies that adaptive motion     vector difference resolution is used in motion vector coding.     amvr_enabled_flag equal to 0 specifies that adaptive motion vector     difference resolution is not used in motion vector coding. -   sps_bdof_enabled_flag equal to 0 specifies that the bi-directional     optical flow inter prediction is disabled. sps_bdof_enabled_flag     equal to 1 specifies that the bi-directional optical flow inter     prediction is enabled. -   sps_bdof_pic_present_flag equal to 1 specifies that     ph_disable_bdof_flag is present in PHs referring to the SPS.     sps_bdof_pic_present_flag equal to 0 specifies that     ph_disable_bdof_flag is not present in PHs referring to the SPS.     When sps_bdof_pic_present_flag is not present, the value of     sps_bdof_pic_present_flag is inferred to be equal to 0. -   sps_smvd_enabled_flag equal to 1 specifies that symmetric motion     vector difference may be used in motion vector decoding.     sps_smvd_enabled_flag equal to 0 specifies that symmetric motion     vector difference is not used in motion vector coding. -   sps_dmvr_enabled_flag equal to 1 specifies that decoder motion     vector refinement based inter bi-prediction is enabled.     sps_dmvr_enabled_flag equal to 0 specifies that decoder motion     vector refinement based inter bi-prediction is disabled. -   sps_dmvr_pic_present_flag equal to 1 specifies that     ph_disable_dmvr_flag is present in PHs referring to the SPS.     sps_dmvr_pic_present_flag equal to 0 specifies that     ph_disable_dmvr_flag is not present in PHs referring to the SPS.     When sps_dmvr_pic_present_flag is not present, the value of     sps_dmvr_pic_present_flag is inferred to be equal to 0. -   sps_mmvd_enabled_flag equal to 1 specifies that merge mode with     motion vector difference is enabled. sps_mmvd_enabled_flag equal to     0 specifies that merge mode with motion vector difference is     disabled. -   sps_isp_enabled_flag equal to 1 specifies that intra prediction with     subpartitions is enabled. sps_isp_enabled_flag equal to 0 specifies     that intra prediction with subpartitions is disabled. -   sps_mrl_enabled_flag equal to 1 specifies that intra prediction with     multiple reference lines is enabled. sps_mrl_enabled_flag equal to 0     specifies that intra prediction with multiple reference lines is     disabled. -   sps_mip_enabled_flag equal to 1 specifies that matrix-based intra     prediction is enabled. sps_mip_enabled_flag equal to 0 specifies     that matrix-based intra prediction is disabled. -   sps_cclm_enabled_flag equal to 0 specifies that the cross-component     linear model intra prediction from luma component to chroma     component is disabled. sps_cclm_enabled_flag equal to 1 specifies     that the cross-component linear model intra prediction from luma     component to chroma componenent is enabled. When     sps_cclm_enabled_flag is not present, it is inferred to be equal to     0. -   sps_chroma_horizontal_collocated_flag equal to 1 specifies that     prediction processes operate in a manner designed for chroma sample     positions that are not horizontally shifted relative to     corresponding luma sample positions.     sps_chroma_horizontal_collocated_flag equal to 0 specifies that     prediction processes operate in a manner designed for chroma sample     positions that are shifted to the right by 0.5 in units of luma     samples relative to corresponding luma sample positions. When     sps_chroma_horizontal_collocated_flag is not present, it is inferred     to be equal to 1. -   sps_chroma_vertical_collocated_flag equal to 1 specifies that     prediction processes operate in a manner designed for chroma sample     positions that are not vertically shifted relative to corresponding     luma sample positions. sps_chroma_vertical_collocated_flag equal to     0 specifies that prediction processes operate in a manner designed     for chroma sample positions that are shifted downward by 0.5 in     units of luma samples relative to corresponding luma sample     positions. When sps_chroma_vertical_collocated_flag is not present,     it is inferred to be equal to 1. -   sps_mts_enabled_flag equal to 1 specifies that     sps_explicit_mts_intra_enabled_flag is present in the sequence     parameter set RBSP syntax and sps_explicit_mts_inter_enabled_flag is     present in the sequence parameter set RBSP syntax.     sps_mts_enabled_flag equal to 0 specifies that     sps_explicit_mts_intra_enabled_flag is not present in the sequence     parameter set RBSP syntax and sps_explicit_mts_inter_enabled_flag is     not present in the sequence parameter set RBSP syntax. -   sps_explicit_mts_intra_enabled_flag equal to 1 specifies that     mts_idx may be present in intra coding unit syntax.     sps_explicit_mts_intra_enabled_flag equal to 0 specifies that     mts_idx is not present in intra coding unit syntax. When not     present, the value of sps_explicit_mts_intra_enabled_flag is     inferred to be equal to 0. -   sps_explicit_mts_inter_enabled_flag equal to 1 specifies that     mts_idx may be present in inter coding unit syntax.     sps_explicit_mts_inter_enabled_flag equal to 0 specifies that     mts_idx is not present in inter coding unit syntax. When not     present, the value of sps_explicit_mts_inter_enabled_flag is     inferred to be equal to 0. -   six_minus_max_num_merge_cand specifies the maximum number of merging     motion vector prediction (MVP) candidates supported in the SPS     subtracted from 6. The maximum number of merging MVP candidates,     MaxNumMergeCand, is derived as follows: -   MaxNumMergeCand=6−six_minus_max_num_merge_cand The value of     MaxNumMergeCand shall be in the range of 1 to 6, inclusive. -   sps_sbt_enabled_flag equal to 0 specifies that subblock transform     for inter-predicted CUs is disabled. sps_sbt_enabled_flag equal to 1     specifies that subblock transform for inter-predicteds CU is     enabled. -   sps_affine_enabled_flag specifies whether affine model based motion     compensation can be used for inter prediction. If     sps_affine_enabled_flag is equal to 0, the syntax shall be     constrained such that no affine model based motion compensation is     used in the CLVS, and inter_affine_flag and cu_affine_type_flag are     not present in coding unit syntax of the CLVS. Otherwise     (sps_affine_enabled_flag is equal to 1), affine model based motion     compensation can be used in the CLVS. -   five_minus_max_num_subblock_merge_cand specifies the maximum number     of subblock-based merging motion vector prediction candidates     supported in the SPS subtracted from 5. -   sps_affine_type_flag specifies whether 6-parameter affine model     based motion compensation can be used for inter prediction. If     sps_affine_type_flag is equal to 0, the syntax shall be constrained     such that no 6-parameter affine model based motion compensation is     used in the CLVS, and cu_affine_type_flag is not present in coding     unit syntax in the CLVS. Otherwise (sps_affine_type_flag is equal to     1), 6-parameter affine model based motion compensation can be used     in the CLVS. When not present, the value of sps_affine_type_flag is     inferred to be equal to 0. -   sps_affine_amvr_enabled_flag equal to 1 specifies that adaptive     motion vector difference resolution is used in motion vector coding     of affine inter mode. sps_affine_amvr_enabled_flag equal to 0     specifies that adaptive motion vector difference resolution is not     used in motion vector coding of affine inter mode. When not present,     the value of sps_affine_amvr_enabled_flag is inferred to be equal to     0. -   sps_affine_prof_enabled_flag specifies whether the prediction     refinement with optical flow can be used for affine motion     compensation. If sps_affine_prof_enabled_flag is equal to 0, the     affine motion compensation shall not be refined with optical flow.     Otherwise (sps_affine_prof_enabled_flag is equal to 1), the affine     motion compensation can be refined with optical flow. When not     present, the value of sps_affine_prof_enabled_flag is inferred to be     equal to 0. -   sps_prof_pic_present_flag equal to 1 specifies that     ph_disable_prof_flag is present in PHs referring to the SPS.     sps_prof_pic_present_flag equal to 0 specifies that     ph_disable_prof_flag is not present in PHs referring to the SPS.     When sps_prof_pic_present_flag is not present, the value of     sps_prof_pic_present_flag is inferred to be equal to 0. -   sps_palette_enabled_flag equal to 1 specifies that     pred_mode_plt_flag may be present in the coding unit syntax.     sps_palette_enabled_flag equal to 0 specifies that     pred_mode_plt_flag is not present in the coding unit syntax. When     sps_palette_enabled_flag is not present, it is inferred to be equal     to 0. -   sps_act_enabled_flag equal to 1 specifies that adaptive colour     transform may be used and the cu_act_enabled_flag may be present in     the coding unit syntax. sps_act_enabled_flag equal to 0 speifies     that adaptive colour transform is not used and cu_act_enabled_flag     is not present in the coding unit syntax. When sps_act_enabled_flag     is not present, it is inferred to be equal to 0. -   min_qp_prime_ts_minus4 specifies the minimum allowed quantization     parameter for transform skip mode as follows: -   QpPrimeTsMin=4+min_qp_prime_ts_minus4 -   The value of min_qp_prime_ts_minus4 shall be in the range of 0 to     48, inclusive. -   sps_bcw_enabled_flag specifies whether bi-prediction with CU weights     can be used for inter prediction. If sps_bcw_enabled_flag is equal     to 0, the syntax shall be constrained such that no bi-prediction     with CU weights is used in the CLVS, and bcw_idx is not present in     coding unit syntax of the CLVS. Otherwise (sps_bcw_enabled_flag is     equal to 1), bi-prediction with CU weights can be used in the CLVS. -   sps_ibc_enabled_flag equal to 1 specifies that the IBC prediction     mode may be used in decoding of pictures in the CLVS.     sps_ibc_enabled_flag equal to 0 specifies that the IBC prediction     mode is not used in the CLVS. When sps_ibc_enabled_flag is not     present, it is inferred to be equal to 0. -   six_minus_max_num_ibc_merge_cand specifies the maximum number of IBC     merging block vector prediction (BVP) candidates supported in the     SPS subtracted from 6. -   The maximum number of IBC merging BVP candidates,     MaxNumIbcMergeCand, is derived as follows:

if( sps_ibc_enabled_flag )  MaxNumIbcMergeCand = 6 − six_minus_max_num_ibc_merge_cand else  MaxNumIbcMergeCand = 0

-   sps_ciip_enabled_flag specifies that ciip_flag may be present in the     coding unit syntax for inter coding units. sps_ciip_enabled_flag     equal to 0 specifies that ciip_flag is not present in the coding     unit syntax for inter coding units. -   sps_fpel_mmvd_enabled_flag equal to 1 specifies that merge mode with     motion vector difference is using integer sample precision.     sps_fpel_mmvd_enabled_flag equal to 0 specifies that merge mode with     motion vector difference can use fractional sample precision. -   sps_gpm_enabled_flag specifies whether geometric partition based     motion compensation can be used for inter prediction.     sps_gpm_enabled_flag equal to 0 specifies that the syntax shall be     constrained such that no geometric partition based motion     compensation is used in the CLVS, and merge_gpm_partition_idx,     merge_gpm_idx0, and merge_gpm_idxl are not present in coding unit     syntax of the CLVS. sps_gpm_enabled_flag equal to 1 specifies that     geometric partition based motion compensation can be used in the     CLVS. When not present, the value of sps_gpm_enabled_flag is     inferred to be equal to 0. -   max_num_merge_cand_minus_max_num_gpm_cand specifies the maximum     number of geometric partitioning merge mode candidates supported in     the SPS subtracted from MaxNumMergeCand. -   If sps_gpm_enabled_flag is equal to 1 and MaxNumMergeCand is greater     than or equal to 3, the maximum number of geometric partitioning     merge mode candidates, MaxNumGeoMergeCand, is derived as follows:

if( sps_gpm_enabled_flag && MaxNumMergeCand >= 3 )  MaxNumGpmMergeCand = MaxNumMergeCand−   max_num_merge_cand_minus_max_num_gpm_cand else if( sps_gpm_enabled_flag && MaxNumMergeCand = = 2 )  MaxNumMergeCand = 2 else  MaxNumGeoMergeCand = 0

-   The value of MaxNumGeoMergeCand shall be in the range of 2 to     MaxNumMergeCand, inclusive. -   sps_lmcs_enabled_flag equal to 1 specifies that luma mapping with     chroma scaling is used in the CLVS. sps_lmcs_enabled_flag equal to 0     specifies that luma mapping with chroma scaling is not used in the     CLVS. -   sps_lfnst_enabled_flag equal to 1 specifies that lfnst_idx may be     present in intra coding unit syntax. sps_lfnst_enabled_flag equal to     0 specifies that lfnst_idx is not present in intra coding unit     syntax. -   sps_ladf_enabled_flag equal to 1, specifies that     sps_num_ladf_intervals_minus2, sps_ladf_lowest_interval_qp_offset,     sps_ladf_qp_offset[i], and sps_ladf_delta_threshold_minus1[i] are     present in the SPS. -   sps_num_ladf_intervals_minus2 plus 1 specifies the number of     sps_ladf_delta_threshold_minus1[i] and sps_ladf_qp_offset[i] syntax     elements that are present in the SPS. The value of     sps_num_ladf_intervals_minus2 shall be in the range of 0 to 3,     inclusive. -   sps_ladf_lowest_interval_qp_offset specifies the offset used to     derive the variable qP as specified. The value of     sps_ladf_lowest_interval_qp_offset shall be in the range of −63 to     63, inclusive. -   sps_ladf_qp_offset[i] specifies the offset array used to derive the     variable qP as specified. The value of sps_ladf_qp_offset[i] shall     be in the range of −63 to 63, inclusive. -   sps_ladf_delta_threshold_minus1[i] is used to compute the values of     SpsLadflntervalLowerBound[i], which specifies the lower bound of the     i-th luma intensity level interval. The value of     sps_ladf_delta_threshold_minus1[i] shall be in the range of 0 to     2^(BitDepth) −3, inclusive. -   The value of SpsLadflntervalLowerBound[0] is set equal to 0. -   For each value of i in the range of 0 to     sps_num_ladf_intervals_minus2, inclusive, the variable     SpsLadflntervalLowerBound[i+1] is derived as follows: -   SpsLadflntervalLowerBound[i+1]=SpsLadflntervalLowerBound[i]+sps_ladf_delta_threshold_minus1[i]+1 -   log2_parallel_merge_level_minus2 plus 2 specifies the value of the     variable Log2ParMrgLevel, which is used in the derivation process     for spatial merging candidates as specified, the derivation process     for motion vectors and reference indices in subblock merge mode as     specified, and to control the invocation of the updating process for     the history-based motion vector predictor list. The value of     log2_parallel_merge_level_minus2 shall be in the range of 0 to     CtbLog2SizeY−2, inclusive. The variable Log2ParMrgLevel is derived     as follows: -   Log2ParMrgLevel=log2_parallel_merge_level_minus2+2 -   sps_scaling_list_enabled_flag equal to 1 specifies that a scaling     list is used for the scaling process for transform coefficients.     sps_scaling_list_enabled_flag equal to 0 specifies that scaling list     is not used for the scaling process for transform coefficients. -   sps_dep_quant_enabled_flag equal to 0 specifies that dependent     quantization is disabled for pictures referring to the SPS.     sps_dep_quant_enabled_flag equal to 1 specifies that dependent     quantization may be enabled for pictures referring to the SPS. -   sps_sign_data_hiding_enabled_flag equal to 0 specifies that sign bit     hiding is disabled for pictures referring to the SPS.     sps_sign_data_hiding_enabled_flag equal to 1 specifies that sign bit     hiding may be enabled for pictures referring to the SPS. When     sps_sign_data_hiding_enabled_flag is not present, it is inferred to     be equal to 0. -   sps_virtual_boundaries_enabled_flag equal to 1 specifies that     disabling in-loop filtering across virtual boundaries may be applied     in the coded pictures in the CLVS.     sps_virtual_boundaries_enabled_flag equal to 0 specifies that     disabling in-loop filtering across virtual boundaries is not applied     in the coded pictures in the CLVS. In-loop filtering operations     include the deblocking filter, sample adaptive offset filter, and     adaptive loop filter operations. -   sps_virtual_boundaries_present_flag equal to 1 specifies that     information of virtual boundaries is signalled in the SPS.     sps_virtual_boundaries_present_flag equal to 0 specifies that     information of virtual boundaries is not signalled in the SPS. When     there is one or more than one virtual boundaries signalled in the     SPS, the in-loop filtering operations are disabled across the     virtual boundaries in pictures referring to the SPS. In-loop     filtering operations include the deblocking filter, sample adaptive     offset filter, and adaptive loop filter operations. It is a     requirement of bitstream conformance that when the value of     res_change_in_clvs_allowed_flag is equal to 1, the value of     sps_virtual_boundaries_present_flag shall be equal to 0. -   sps_num_ver_virtual_boundaries specifies the number of     sps_virtual_boundaries_pos_x[i] syntax elements that are present in     the SPS. When sps_num_ver_virtual_boundaries is not present, it is     inferred to be equal to 0. -   sps_virtual_boundaries_pos_x[i] specifies the location of the i-th     vertical virtual boundary in units of luma samples divided by 8. The     value of sps_virtual_boundaries_pos_x[i] shall be in the range of 1     to Ceil(pic_width_in_luma_samples÷8)−1, inclusive. -   sps_num_hor_virtual_boundaries specifies the number of     sps_virtual_boundaries_pos_y[i] syntax elements that are present in     the SPS. When sps_num_hor_virtual_boundaries is not present, it is     inferred to be equal to 0. -   When sps_virtual_boundaries_enabled_flag is equal to 1 and     sps_virtual_boundaries_present_flag is equal to 1, the sum of     sps_num_ver_virtual_boundaries and sps_num_hor_virtual_boundaries     shall be greater than 0. -   sps_virtual_boundaries_pos_y[i] specifies the location of the i-th     horizontal virtual boundary in units of luma samples divided by 8.     The value of sps_virtual_boundaries_pos_y[i] shall be in the range     of 1 to Ceil(pic_height_in_luma_samples÷8)−1, inclusive. -   sps_general_hrd_params_present_flag equal to 1 specifies that the     syntax structure general_hrd_parameters( ) is present in the SPS     RBSP syntax structure. sps_general_hrd_params_present_flag equal to     0 specifies that the syntax structure general_hrd_parameters( ) is     not present in the SPS RBSP syntax structure. -   sps_sublayer_cpb_params_present_flag equal to 1 specifies that the     syntax structure old_hrd_parameters( ) in the SPS RBSP includes HRD     parameters for sublayer representations with TemporalId in the range     of 0 to sps_max_sublayers_minus1, inclusive.     sps_sublayer_cpb_params_present_flag equal to 0 specifies that the     syntax structure ols_hrd_parameters( ) in the SPS RBSP includes HRD     parameters for the sublayer representation with TemporalId equal to     sps_max_sublayers_minus1 only. When sps_max_sublayers_minus1 is     equal to 0, the value of sps_sublayer_cpb_params_present_flag is     inferred to be equal to 0. -   When sps_sublayer_cpb_params_present_flag is equal to 0, the HRD     parameters for the sublayer representations with TemporalId in the     range of 0 to sps_max_sublayers_minus1−1, inclusive, are inferred to     be the same as that for the sublayer representation with TemporalId     equal to sps_max_sublayers_minus1. These include the HRD parameters     starting from the fixed_pic_rate_general_flag[i] syntax element till     the sublayer_hrd_parameters(i) syntax structure immediately under     the condition “if(general_vcl_hrd_params_present_flag)” in the     ols_hrd_parameters syntax structure. -   field_seq_flag equal to 1 indicates that the CLVS conveys pictures     that represent fields. field_seq_flag equal to 0 indicates that the     CLVS conveys pictures that represent frames. When     general_frame_only_constraint_flag is equal to 1, the value of     field_seq_flag shall be equal to 0. When field_seq_flag is equal to     1, a frame-field information SEI message shall be present for every     coded picture in the CLVS. -   NOTE—The specified decoding process does not treat pictures that     represent fields or frames differently. A sequence of pictures that     represent fields would therefore be coded with the picture     dimensions of an individual field. For example, pictures that     represent 1080i fields would commonly have cropped output dimensions     of 1920×540, while the sequence picture rate would commonly express     the rate of the source fields (typically between 50 and 60 Hz),     instead of the source frame rate (typically between 25 and 30 Hz). -   vui_parameters_present_flag equal to 1 specifies that the syntax     structure vui_parameters( ) is present in the SPS RBSP syntax     structure. vui_parameters_present_flag equal to 0 specifies that the     syntax structure vui_parameters( ) is not present in the SPS RBSP     syntax structure. -   sps_extension_flag equal to 0 specifies that no     sps_extension_data_flag syntax elements are present in the SPS RBSP     syntax structure. sps_extension_flag equal to 1 specifies that there     are sps_extension_data_flag syntax elements present in the SPS RBSP     syntax structure. -   sps_extension_data__flag may have any value. Its presence and value     do not affect decoder conformance to profiles specified in this     version of this Specification. Decoders conforming to this version     of this Specification shall ignore all sps_extension_data_flag     syntax elements. -   As provided above, in WET-Q2001, a VPS or an SPS may include a     general_hrd_parameters( ) syntax structure. Table 7 illustrates the     general hrdparameters( ) syntax structure provided in WET-Q2001.

TABLE 7 Descriptor general_hrd_parameters( ) {  num_units_in_tick u(32)  times_cale u(32)  general_nal_hrd_params_present_flag u(1)  general_vcl_hrd_params_present_flag u(1)  general_same_pic_timing_in_all_ols_flag u(1)  general_decoding_unit_hrd_params_present_flag u(1)  if( general_decoding_unit_hrd_params_present_flag )   tick_divisor_minus2 u(8)  bit_rate_scale u(4)  cpb_size_scale u(4)  if( general_decoding_unit_hrd_params_present_flag )   cpb_size_du_scale u(4)  hrd_cpb_cnt_minus1 ue(v) }

With respect to Table 7, WET-Q2001 provides the following semantics:

-   The general_hrd_parameters( ) syntax structure provides some of the     sequence-level HRD parameters used in the HRD operations. -   It is a requirement of bitstream conformance that the content of the     general_hrd_parameters( ) syntax structure present in any VPSs or     SPSs in the bitstream shall be identical. -   When included in a VPS, the general_hrd_parameters( ) syntax     structure applies to all OLSs specified by the VPS. When included in     an SPS, the general_hrd_parameters( ) syntax structure applies to     the OLS that includes only the layer that is the lowest layer among     the layers that refer to the SPS, and this lowest layer is an     independent layer. -   num_units_in_tick is the number of time units of a clock operating     at the frequency time_scale Hz that corresponds to one increment     (called a clock tick) of a clock tick counter. num_units_in_tick     shall be greater than 0. A clock tick, in units of seconds, is equal     to the quotient of num_units_in_tick divided by time_scale. For     example, when the picture rate of a video signal is 25 Hz,     time_scale may be equal to 27 000 000 and num_units_in_tick may be     equal to 1 080 000, and consequently a clock tick may be equal to     0.04 seconds. -   time_scale is the number of time units that pass in one second. For     example, a time coordinate system that measures time using a 27 MHz     clock has a time_scale of 27 000 000. The value of time_scale shall     be greater than 0. -   general_nal_hrd_params_present_flag equal to 1 specifies that NAL     HRD parameters (pertaining to Type II bitstream conformance point)     are present in the general_hrd_parameters( ) syntax structure.     general_nal_hrd_params_present_flag equal to 0 specifies that NAL     HRD parameters are not present in the general_hrd_parameters( )     syntax structure.     -   NOTE—When general_nal_hrd_params_present_flag is equal to 0, the         conformance of the bitstream cannot be verified without         provision of the NAL HRD parameters and all BP SEI messages,         and, when general_vcl_hrd_params_present_flag is also equal to         0, all PT and DU information SEI messages, by some means not         specified in this Specification. -   The variable NalHrdBpPresentFlag is derived as follows:     -   If one or more of the following conditions are true, the value         of NalHrdBpPresentFlag is set equal to 1:         -   general_nal_hrd_params_present_flag is present in the             bitstream and is equal to 1.         -   The need for presence of BPs for NAL HRD operation to be             present in the bitstream in BP SEI messages is determined by             the application, by some means not specified in this             Specification.     -   Otherwise, the value of NalHrdBpPresentFlag is set equal to 0. -   general_vcl_hrd_params_present_flag equal to 1 specifies that VCL     HRD parameters (pertaining to Type I bitstream conformance point)     are present in the general_hrd_parameters( ) syntax structure.     general_vcl_hrd_params_present_flag equal to 0 specifies that VCL     HRD parameters are not present in the general_hrd_parameters( )     syntax structure.     -   NOTE—When general_vcl_hrd_params_present_flag is equal to 0, the         conformance of the bitstream cannot be verified without         provision of the VCL HRD parameters and all BP SEI messages, and         when general_nal_hrd_params_present_flag is also equal to 0, all         PT and DU information SEI messages, by some means not specified. -   The variable VclHrdBpPresentFlag is derived as follows:     -   If one or more of the following conditions are true, the value         of VclHrdBpPresentFlag is set equal to 1:         -   general_vcl_hrd_params_present_flag is present in the             bitstream and is equal to 1.         -   The need for presence of BPs for VCL HRD operation to be             present in the bitstream in BP SEI messages is determined by             the application, by some means not specified.     -   Otherwise, the value of VclHrdBpPresentFlag is set equal to 0. -   The variable CpbDpbDelaysPresentFlag is derived as follows:     -   If one or more of the following conditions are true, the value         of CpbDpbDelaysPresentFlag is set equal to 1:         -   general_nal_hrd_params_present_flag is present in the             bitstream and is equal to 1.         -   general_vcl_hrd_params_present_flag is present in the             bitstream and is equal to 1.         -   The need for presence of CPB and DPB output delays to be             present in the bitstream in PT SEI messages is determined by             the application, by some means not specified.     -   Otherwise, the value of CpbDpbDelaysPresentFlag is set equal to         0. -   It is a requirement of bitstream conformance that the values of     general_nal_hrd_params_present_flag and     general_vcl_hrd_params_present_flag in each general_hrd_parameters(     ) syntax structure shall not be both equal to 0. -   general_same_pic_timing_in_all_ols_flag equal to 1 specifies that     the non-scalable-nested PT SEI message in each AU applies to the AU     for any OLS in the bitstream and no scalable-nested PT SEI messages     are present. general_same_pic_timing_in_all_ols_flag equal to 0     specifies that the non-scalable-nested PT SEI message in each AU may     or may not apply to the AU for any OLS in the bitstream and     scalable-nested PT SEI messages may be present. -   general_decoding_unit_hrd_params_present_flag equal to 1 specifies     that DU level HRD parameters are present and the HRD may operate at     AU level or DU level. general_decoding_unit_hrd_params_present_flag     equal to 0 specifies that DU level HRD parameters are not present     and the HRD operates at AU level. When     general_decoding_unit_hrd_params_present_flag is not present, its     value is inferred to be equal to 0. -   tick_divisor_minus2 is used to specify the clock sub-tick. A clock     sub-tick is the minimum interval of time that can be represented in     the coded data when general_decoding_unit_hrd_params_present_flag is     equal to 1. -   bit_rate_scale (together with bit_rate_value_minus1[i][j]) specifies     the maximum input bit rate of the j-th CPB when Htid is equal to i. -   cpb_size_scale (together with cpb_size_value_minus1[i][j]) specifies     the CPB size of the j-th CPB when Htid is equal to i and when the     CPB operates at the AU level. -   cpb_size_du_scale (together with cpb_size_du_value_minus1[i][j])     specifies the CPB size of the j-th CPB when Htid is equal to i and     when the CPB operates at DU level. -   hrd_cpb_cnt_minus1 plus 1 specifies the number of alternative CPB     delivery schedules. The value of hrd_cpb_cnt_minus1 shall be in the     range of 0 to 31, inclusive.

With respect to profiles, tiers, and levels, JVET-Q2001 provides the following:

Profiles Main 10 Profile

-   Bitstreams conforming to the Main 10 profile shall obey the     following constraints:     -   Referenced SPSs shall have chroma_format_idc equal to 0 or 1.     -   Referenced SPSs shall have bit_depth_minus8 in the range of 0 to         2, inclusive.     -   Referenced SPSs shall have sps_palette_enabled_flag equal to 0.     -   general_level_idc and sublayer_level_idc[i] for all values of i         in the VPS (when available) and in the referenced SPSs shall not         be equal to 255 (which indicates level 8.5).     -   The tier and level constraints specified for the Main 10 profile         below, as applicable, shall be fulfilled. -   Conformance of a bitstream to the Main 10 profile is indicated by     general_profile_idc being equal to 1. -   Decoders conforming to the Main 10 profile at a specific level of a     specific tier shall be capable of decoding all bitstreams for which     all of the following conditions apply:     -   The bitstream is indicated to conform to the Main 10 profile.     -   The bitstream is indicated to conform to a tier that is lower         than or equal to the specified tier. -   The bitstream is indicated to conform to a level that is not level     8.5 and is lower than or equal to the specified level.

Main 4:4:4 10 Profile

-   Bitstreams conforming to the Main 4:4:4 10 profile shall obey the     following constraints:     -   Referenced SPSs shall have chroma format idc in the range of 0         to 3, inclusive.     -   Referenced SPSs shall have bit_depth_minus8 in the range of 0 to         2, inclusive.     -   general_level_idc and sublayer_level_idc[i] for all values of i         in the VPS (when available) and in the referenced SPSs shall not         be equal to 255 (which indicates level 8.5).     -   The tier and level constraints specified for the Main 4:4:4 10         profile, as applicable, shall be fulfilled. -   Conformance of a bitstream to the Main 4:4:4 10 profile is indicated     by general_profile_idc being equal to 2. -   Decoders conforming to the Main 4:4:4 10 profile at a specific level     of a specific tier shall be capable of decoding all bitstreams for     which all of the following conditions apply:     -   The bitstream is indicated to conform to the Main 4:4:4 10 or         Main 10 profile.     -   The bitstream is indicated to conform to a tier that is lower         than or equal to the specified tier.     -   The bitstream is indicated to conform to a level that is not         level 8.5 and is lower than or equal to the specified level.

General Tier and Level Limits

-   For purposes of comparison of tier capabilities, the tier with     general_tier_flag equal to 0 is considered to be a lower tier than     the tier with general_tier_flag equal to 1. -   For purposes of comparison of level capabilities, a particular level     of a specific tier is considered to be a lower level than some other     level of the same tier when the value of the general_level_idc or     sublayer_level_idc[i] of the particular level is less than that of     the other level. -   The following is specified for expressing the constraints in this     annex:     -   Let AU n be the n-th AU in decoding order, with the first AU         being AU 0 (i.e., the 0-th AU).     -   For an OLS with OLS index TargetOlsIdx, the variables         PicWidthMaxInSamplesY, PicHeightMaxInSamplesY, and         PicSizeMaxInSamplesY, and the applicable dpb_parameters( )         syntax structure are derived as follows:         -   If NumLayersInOls[TargetOlsIdx] is equal to 1,             PicWidthMaxInSamplesY is set equal to             pic_width_max_in_luma_samples, PicHeightMaxInSamplesY is set             equal to pic_height_max_in_luma_samples,             PicSizeMaxInSamplesY is set equal to PicWidthMaxInSamplesY *             PicHeightMaxInSamplesY, where pic_width_max_in_luma samples             and pic_height_max_in_luma_samples are found in the SPS             referred to by the layer in the OLS, and the applicable             dpb_parameters( ) syntax structure is also found in that             SPS.         -   Otherwise (NumLayersInOls[TargetOlsIdx] is greater than 1),             PicWidthMaxInSamplesY is set equal to             ols_dpb_pic_width[TargetOlsIdx], PicHeightMaxInSamplesY is             set equal to ols_dpb_pic_height[TargetOlsIdx],             PicSizeMaxInSamplesY is set equal to PicWidthMaxInSamplesY *             PicHeightMaxInSamplesY, and the applicable dpb_parameters( )             syntax structure is identified by             ols_dpb_params_idx[TargetOlsIdx] found in the VPS. -   When the specified level is not level 8.5, bitstreams conforming to     a profile at a specified tier and level shall obey the following     constraints for each bitstream conformance test as specified:     -   a) PicSizeMaxInSamplesY shall be less than or equal to         MaxLumaPs, where MaxLumaPs is specified in Table 8.     -   b) The value of PicWidthMaxInSamplesY shall be less than or         equal to Sqrt(MaxLumaPs * 8).     -   c) The value of PicHeightMaxInSamplesY shall be less than or         equal to Sqrt(MaxLumaPs * 8).     -   d) For each referenced PPS, the value of NumTileColumns shall be         less than or equal to MaxTileCols and the value of NumTileRows         shall be less than or equal to MaxTileRows, where MaxTileCols         and MaxTileRows are specified in Table 8.     -   e) For the VCL HRD parameters, CpbSize[Htid][i] shall be less         than or equal to CpbVclFactor * MaxCPB for at least one value of         i in the range of 0 to hrd_cpb_cnt_minus1, inclusive, where         CpbSize[Htid][i] is specified as provided above based on         parameters selected as specified, CpbVclFactor is specified in         Table 10 and MaxCPB is specified in Table 8 in units of         CpbVclFactor bits.     -   f) For the NAL HRD parameters, CpbSize[Htid][i] shall be less         than or equal to CpbNalFactor * MaxCPB for at least one value of         i in the range of 0 to hrd_cpb_cnt_minus1, inclusive, where         CpbSize[Htid][i] is specified as provided above based on         parameters selected as specified, CpbNalFactor is specified in         Table 10, and MaxCPB is specified in Table 8 in units of         CpbNalFactor bits. -   Table 8 specifies the limits for each level of each tier for levels     other than level 8.5. -   A tier and level to which a bitstream conforms are indicated by the     syntax elements general_tier_flag and general_level_idc, and a level     to which a sublayer representation conforms are indicated by the     syntax element sublayer_level_idc[i], as follows:     -   If the specified level is not level 8.5, general_tier_flag equal         to 0 indicates conformance to the Main tier, general_tier_flag         equal to 1 indicates conformance to the High tier, according to         the tier constraints specified in Table 8 and general_tier_flag         shall be equal to 0 for levels below level 4 (corresponding to         the entries in Table 8 marked with “-”). Otherwise (the         specified level is level 8.5), it is a requirement of bitstream         conformance that general_tier_flag shall be equal to 1 and the         value 0 for general_tier_flag is reserved for future use by         ITU-T | ISO/IEC and decoders shall ignore the value of         general_tier_flag.     -   general_level_idc and sublayer_level_idc[i] shall be set equal         to a value of 30 times the level number specified in Table 8.

TABLE 8 Max CPB size MaxCPB Max # Max # Max luma (CpbVclFact Max slices of tile of tile picture size or or per picture rows columns MaxLumaPs Main High MaxSlices MaxTile MaxTile Level (samples) tier tier PerPicture Rows Cols 1      36 864    350 —  16  1  1 2     122 880  1 500 —  16  1  1 2.1   245 760  3 000 —  20  1  1 3     552 960  6 000 —  30  2  2 3.1   983 040  10 000 —  40  3  3 4    2 228 224  12 000  30 000  75  5  5 4.1  2 228 224  20 000  50 000  75  5  5 5    8 912 896  25 000 100 000 200 11 10 5.1  8 912 896  40 000 160 000 200 11 10 5.2  8 912 896  60 000 240 000 200 11 10 6   35 651 584  60 000 240 000 600 22 20 6.1 35 651 584 120 000 480 000 600 22 20 6.2 35 651 584 240 000 800 000 600 22 20

Profile-Specific Level Limits

-   The following is specified for expressing the constraints in this     annex:     -   Let the variable fR be set equal to 1÷300. -   The variable HbrFactor is defined as follows:     -   If the bitstream is indicated to conform to the Main 10 profile         or the Main 4:4:4 10 profile, HbrFactor is set equal to 1. -   The variable BrVclFactor, which represents the VCL bit rate scale     factor, is set equal to CpbVclFactor * HbrFactor. -   The variable BrNalFactor, which represents the NAL bit rate scale     factor, is set equal to CpbNalFactor * HbrFactor. -   The variable MinCr is set equal to MinCrBase *     MinCrScaleFactor÷HbrFactor. -   When the specified level is not level 8.5, the value of     max_dec_pic_buffering_minus1[Htid]+1 shall be less than or equal to     MaxDpbSize, which is derived as follows:

if( PicSizeMaxInSamplesY <= ( MaxLumaPs >> 2 ) )  MaxDpbSize = Min( 4 * maxDpbPicBuf, 16 ) else if( PicSizeMaxInSamplesY <= ( MaxLumaPs >> 1 ) )  MaxDpbSize = Min( 2 * maxDpbPicBuf, 16 ) else if( PicSizeMaxInSamplesY <= ( ( 3 * MaxLumaPs ) >> 2 ) )  MaxDpbSize = Min( ( 4 * maxDpbPicBuf ) / 3, 16 ) else  MaxDpbSize = maxDpbPicBuf

-   where MaxLumaPs is specified in Table 8, maxDpbPicBuf is equal to 8,     and max_dec_pic_buffering_minus1[Htid] is found in or derived from     the applicable dpb_parameters( ) syntax structure. -   Let numDecPics be the number of pictures in AU n. The variable     AuSizeMaxInSamplesY[n] is set equal to PicSizeMaxInSamplesY *     numDecPics. -   Bitstreams conforming to the Main 10 or Main 4:4:4 10 profile at a     specified tier and level shall obey the following constraints for     each bitstream conformance test as specified:     -   a) The nominal removal time of AU n (with n greater than 0) from         the CPB, as specified, shall satisfy the constraint that         AuNominalRemovalTime[n]−AuCpbRemovalTime[n−1] is greater than or         equal to Max(AuSizeMaxInSamplesY[n−1]÷MaxLumaSr, fR), where         MaxLumaSr is the value specified in that applies to AU n−1.     -   b) The difference between consecutive output times of pictures         of different AUs from the DPB, as specified, shall satisfy the         constraint that DpbOutputInterval[n] is greater than or equal to         Max(AuSizeMaxInSamplesY[n÷MaxLumaSr, fR), where MaxLumaSr is the         value specified in Table 9 for AU n, provided that AU n has a         picture that is output and AU n is not the last AU of the         bitstream that has a picture that is output.     -   c) The removal time of AU 0 shall satisfy the constraint that         the number of slices in each picture in AU 0 is less than or         equal to Min(Max(1, MaxSlicesPerPicture * MaxLumaSr/MaxLumaPs *         (AuCpbRemovalTime[0]−AuNominalRemovalTime[0])+MaxSlicesPerPicture *         PicSizeMaxInSamplesY/MaxLumaPs), MaxSlicesPerPicture), for the         value of PicSizeMaxInSamplesY of picture 0, where         MaxSlicesPerPicture, MaxLumaPs and MaxLumaSr are the values         specified in Table 8 and Table 9, respectively, that apply to AU         0.     -   d) The difference between consecutive CPB removal times of AUs n         and n−1 (with n greater than 0) shall satisfy the constraint         that the number of slices in each picture in AU n is less than         or equal to Min((Max(1, MaxSlicesPerPicture *         MaxLumaSr/MaxLumaPs *         (AuCpbRemovalTime[n]−AuCpbRemovalTime[n−1)),         MaxSlicesPerPicture), where MaxSlicesPerPicture, MaxLumaPs and         MaxLumaSr are the values specified in Table 8 and Table 9 that         apply to AU n.     -   e) For the VCL HRD parameters, BitRate[Htid][i] shall be less         than or equal to BrVclFactor * MaxBR for at least one value of i         in the range of 0 to hrd_cpb_cnt_minus 1, inclusive, where         BitRate[Htid][i] is specified above based on parameters selected         as specified and MaxBR is specified in Table 9 in units of         BrVclFactor bits/s.     -   f) For the NAL HRD parameters, BitRate[Htid][i] shall be less         than or equal to BrNalFactor * MaxBR for at least one value of i         in the range of 0 to hrd_cpb_cnt_minus1, inclusive, where         BitRate[Htid][i] is specified above based on parameters selected         as specified and MaxBR is specified in Table 9 in units of         BrNalFactor bits/s.     -   g) The sum of the NumBytesInNalUnit variables for AU 0 shall be         less than or equal to FormatCapabilityFactor *         (Max(AuSizeMaxInSamplesY[0], fR * MaxLumaSr)+MaxLumaSr *         (AuCpbRemovalTime[0]−AuNominalRemovalTime[0]))÷MinCr, where         MaxLumaSr and FormatCapabilityFactor are the values specified in         Table 9 and Table 10, respectively, that apply to AU 0.     -   h) The sum of the NumBytesInNalUnit variables for AU n (with n         greater than 0) shall be less than or equal to         FormatCapabilityFactor * MaxLumaSr *         (AuCpbRemovalTime[n]−AuCpbRemovalTime[n−1])÷MinCr, where         MaxLumaSr and FormatCapabilityFactor are the values specified in         Table 7 and Table 8 respectively, that apply to AU n.     -   i) The removal time of AU 0 shall satisfy the constraint that         the number of tiles in each picture in AU 0 is less than or         equal to Min(Max(1, MaxTileCols * MaxTileRows * 120 *         (AuCpbRemovalTime[0]−AuNominalRemovalTime[0])+MaxTileCols *         MaxTileRows * AuSizeMaxInSamplesY[0]/MaxLumaPs), MaxTileCols *         MaxTileRows), where MaxTileCols and MaxTileRows are the values         specified in Table 8 that apply to AU 0.     -   j) The difference between consecutive CPB removal times of AUs n         and n−1 (with n greater than 0) shall satisfy the constraint         that the number of tiles in each picture in AU n is less than or         equal to Min(Max(1, MaxTileCols * MaxTileRows * 120 *         (AuCpbRemovalTime[n]−AuCpbRemovalTime[n−1)), MaxTileCols *         MaxTileRows), where MaxTileCols and MaxTileRows are the values         specified in Table 8 that apply to AU n.

TABLE 9 Max luma sample Max bite rate MaxBR rate MaxLumaSr (BrVclFactor or BrNalFactor Min compression ratio Level (samples/sec) Main tier High tier Main tier High tier 1    552 960   128 — 2 2 2    3 686 400  1 500 — 2 2 2.1    7 372 800  3 000 — 2 2 3   16 588 800  6 000 — 2 2 3.1   33 177 600 10 000 — 2 2 4   66 846 720 12 000  30 000 4 4 4.1   133 693 440 20 000  50 000 4 4 5   267 386 880 25 000 100 000 6 4 5.1   534 773 760 40 000 160 000 8 4 5.2 1 069 547 520 60 000 240 000 8 4 6 1 069 547 520 60 000 240 000 8 4 6.1 2 139 095 040 120 000  480 000 8 4 6.2 4 278 190 080 240 000  800 000 6 4

TABLE 10 Profile CpbVclFactor CpbNalFactor FormatCapabilityFactor MinCrScaleFactor Main 10 1 000 1 100 1.875 1.0 Main 4:4:4 10 2 500 2 750 3.750 0.5

The signaling of DCI information and corresponding profile, tier, level information in NET-Q2001 is less than ideal. For example, the signaling of syntax element dci_max_sublayers_minus1 is unnecessary. That is, syntax element dci_max_sublayers_minus1 could be used as a second input argument to profile_tier_level( ) syntax structure present in decoding_capability_information_rbsp( ). However, since the profile_tier_level( ) syntax structure in DCI does not specify information about sublayers, this syntax element is unnecessary. This disclosure describes techniques for signaling of DCI information and corresponding profile, tier, level information.

FIG. 1 is a block diagram illustrating an example of a system that may be configured to code (i.e., encode and/or decode) video data according to one or more techniques of this disclosure. System 100 represents an example of a system that may encapsulate video data according to one or more techniques of this disclosure. As illustrated in FIG. 1 , system 100 includes source device 102, communications medium 110, and destination device 120. In the example illustrated in FIG. 1 , source device 102 may include any device configured to encode video data and transmit encoded video data to communications medium 110. Destination device 120 may include any device configured to receive encoded video data via communications medium 110 and to decode encoded video data. Source device 102 and/or destination device 120 may include computing devices equipped for wired and/or wireless communications and may include, for example, set top boxes, digital video recorders, televisions, desktop, laptop or tablet computers, gaming consoles, medical imagining devices, and mobile devices, including, for example, smartphones, cellular telephones, personal gaming devices.

Communications medium 110 may include any combination of wireless and wired communication media, and/or storage devices. Communications medium 110 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. Communications medium 110 may include one or more networks. For example, communications medium 110 may include a network configured to enable access to the World Wide Web, for example, the Internet. A network may operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include Digital Video Broadcasting (DVB) standards, Advanced Television Systems Committee (ATSC) standards, Integrated Services Digital Broadcasting (ISDB) standards, Data Over Cable Service Interface Specification (DOCSIS) standards, Global System Mobile Communications (GSM) standards, code division multiple access (CDMA) standards, 3rd Generation Partnership Project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, Internet Protocol (IP) standards, Wireless Application Protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards.

Storage devices may include any type of device or storage medium capable of storing data. A storage medium may include a tangible or non-transitory computer-readable media. A computer readable medium may include optical discs, flash memory, magnetic memory, or any other suitable digital storage media. In some examples, a memory device or portions thereof may be described as non-volatile memory and in other examples portions of memory devices may be described as volatile memory. Examples of volatile memories may include random access memories (RAM), dynamic random access memories (DRAM), and static random access memories (SRAM). Examples of non-volatile memories may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. Storage device(s) may include memory cards (e.g., a Secure Digital (SD) memory card), internal/external hard disk drives, and/or internal/external solid state drives. Data may be stored on a storage device according to a defined file format.

FIG. 4 is a conceptual drawing illustrating an example of components that may be included in an implementation of system 100. In the example implementation illustrated in FIG. 4 , system 100 includes one or more computing devices 402A-402N, television service network 404, television service provider site 406, wide area network 408, local area network 410, and one or more content provider sites 412A-412N. The implementation illustrated in FIG. 4 represents an example of a system that may be configured to allow digital media content, such as, for example, a movie, a live sporting event, etc., and data and applications and media presentations associated therewith to be distributed to and accessed by a plurality of computing devices, such as computing devices 402A-402N. In the example illustrated in FIG. 4 , computing devices 402A-402N may include any device configured to receive data from one or more of television service network 404, wide area network 408, and/or local area network 410. For example, computing devices 402A-402N may be equipped for wired and/or wireless communications and may be configured to receive services through one or more data channels and may include televisions, including so-called smart televisions, set top boxes, and digital video recorders. Further, computing devices 402A-402N may include desktop, laptop, or tablet computers, gaming consoles, mobile devices, including, for example, “smart” phones, cellular telephones, and personal gaming devices.

Television service network 404 is an example of a network configured to enable digital media content, which may include television services, to be distributed. For example, television service network 404 may include public over-the-air television networks, public or subscription-based satellite television service provider networks, and public or subscription-based cable television provider networks and/or over the top or Internet service providers. It should be noted that although in some examples television service network 404 may primarily be used to enable television services to be provided, television service network 404 may also enable other types of data and services to be provided according to any combination of the telecommunication protocols described herein. Further, it should be noted that in some examples, television service network 404 may enable two-way communications between television service provider site 406 and one or more of computing devices 402A-402N. Television service network 404 may comprise any combination of wireless and/or wired communication media. Television service network 404 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. Television service network 404 may operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include DVB standards, ATSC standards, ISDB standards, DTMB standards, DMB standards, Data Over Cable Service Interface Specification (DOCSIS) standards, HbbTV standards, W3C standards, and UPnP standards.

Referring again to FIG. 4 , television service provider site 406 may be configured to distribute television service via television service network 404. For example, television service provider site 406 may include one or more broadcast stations, a cable television provider, or a satellite television provider, or an Internet-based television provider. For example, television service provider site 406 may be configured to receive a transmission including television programming through a satellite uplink/downlink. Further, as illustrated in FIG. 4 , television service provider site 406 may be in communication with wide area network 408 and may be configured to receive data from content provider sites 412A-412N. It should be noted that in some examples, television service provider site 406 may include a television studio and content may originate therefrom.

Wide area network 408 may include a packet based network and operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include Global System Mobile Communications (GSM) standards, code division multiple access (CDMA) standards, 3rd Generation Partnership Project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, European standards (EN), IP standards, Wireless Application Protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards, such as, for example, one or more of the IEEE 802 standards (e.g., Wi-Fi). Wide area network 408 may comprise any combination of wireless and/or wired communication media. Wide area network 408 may include coaxial cables, fiber optic cables, twisted pair cables, Ethernet cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. In one example, wide area network 408 may include the Internet. Local area network 410 may include a packet based network and operate according to a combination of one or more telecommunication protocols. Local area network 410 may be distinguished from wide area network 408 based on levels of access and/or physical infrastructure. For example, local area network 410 may include a secure home network.

Referring again to FIG. 4 , content provider sites 412A-412N represent examples of sites that may provide multimedia content to television service provider site 406 and/or computing devices 402A-402N. For example, a content provider site may include a studio having one or more studio content servers configured to provide multimedia files and/or streams to television service provider site 406. In one example, content provider sites 412A-412N may be configured to provide multimedia content using the IP suite. For example, a content provider site may be configured to provide multimedia content to a receiver device according to Real Time Streaming Protocol (RTSP), HTTP, or the like. Further, content provider sites 412A-412N may be configured to provide data, including hypertext based content, and the like, to one or more of receiver devices computing devices 402A-402N and/or television service provider site 406 through wide area network 408. Content provider sites 412A-412N may include one or more web servers. Data provided by data provider site 412A-412N may be defined according to data formats.

Referring again to FIG. 1 , source device 102 includes video source 104, video encoder 106, data encapsulator 107, and interface 108. Video source 104 may include any device configured to capture and/or store video data. For example, video source 104 may include a video camera and a storage device operably coupled thereto. Video encoder 106 may include any device configured to receive video data and generate a compliant bitstream representing the video data. A compliant bitstream may refer to a bitstream that a video decoder can receive and reproduce video data therefrom. Aspects of a compliant bitstream may be defined according to a video coding standard. When generating a compliant bitstream video encoder 106 may compress video data. Compression may be lossy (discernible or indiscernible to a viewer) or lossless. FIG. 5 is a block diagram illustrating an example of video encoder 500 that may implement the techniques for encoding video data described herein. It should be noted that although example video encoder 500 is illustrated as having distinct functional blocks, such an illustration is for descriptive purposes and does not limit video encoder 500 and/or sub-components thereof to a particular hardware or software architecture. Functions of video encoder 500 may be realized using any combination of hardware, firmware, and/or software implementations.

Video encoder 500 may perform intra prediction coding and inter prediction coding of picture areas, and, as such, may be referred to as a hybrid video encoder. In the example illustrated in FIG. 5 , video encoder 500 receives source video blocks. In some examples, source video blocks may include areas of picture that has been divided according to a coding structure. For example, source video data may include macroblocks, CTUs, CBs, sub-divisions thereof, and/or another equivalent coding unit. In some examples, video encoder 500 may be configured to perform additional sub-divisions of source video blocks. It should be noted that the techniques described herein are generally applicable to video coding, regardless of how source video data is partitioned prior to and/or during encoding. In the example illustrated in FIG. 5 , video encoder 500 includes summer 502, transform coefficient generator 504, coefficient quantization unit 506, inverse quantization and transform coefficient processing unit 508, summer 510, intra prediction processing unit 512, inter prediction processing unit 514, filter unit 516, and entropy encoding unit 518. As illustrated in FIG. 5 , video encoder 500 receives source video blocks and outputs a bitstream.

In the example illustrated in FIG. 5 , video encoder 500 may generate residual data by subtracting a predictive video block from a source video block. The selection of a predictive video block is described in detail below. Summer 502 represents a component configured to perform this subtraction operation. In one example, the subtraction of video blocks occurs in the pixel domain. Transform coefficient generator 504 applies a transform, such as a discrete cosine transform (DCT), a discrete sine transform (DST), or a conceptually similar transform, to the residual block or sub-divisions thereof (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values) to produce a set of residual transform coefficients. Transform coefficient generator 504 may be configured to perform any and all combinations of the transforms included in the family of discrete trigonometric transforms, including approximations thereof. Transform coefficient generator 504 may output transform coefficients to coefficient quantization unit 506. Coefficient quantization unit 506 may be configured to perform quantization of the transform coefficients. The quantization process may reduce the bit depth associated with some or all of the coefficients. The degree of quantization may alter the rate-distortion (i.e., bit-rate vs. quality of video) of encoded video data. The degree of quantization may be modified by adjusting a quantization parameter (QP). A quantization parameter may be determined based on slice level values and/or CU level values (e.g., CU delta QP values). QP data may include any data used to determine a QP for quantizing a particular set of transform coefficients. As illustrated in FIG. 5 , quantized transform coefficients (which may be referred to as level values) are output to inverse quantization and transform coefficient processing unit 508. Inverse quantization and transform coefficient processing unit 508 may be configured to apply an inverse quantization and an inverse transformation to generate reconstructed residual data. As illustrated in FIG. 5 , at summer 510, reconstructed residual data may be added to a predictive video block. In this manner, an encoded video block may be reconstructed and the resulting reconstructed video block may be used to evaluate the encoding quality for a given prediction, transformation, and/or quantization. Video encoder 500 may be configured to perform multiple coding passes (e.g., perform encoding while varying one or more of a prediction, transformation parameters, and quantization parameters). The rate-distortion of a bitstream or other system parameters may be optimized based on evaluation of reconstructed video blocks. Further, reconstructed video blocks may be stored and used as reference for predicting subsequent blocks.

Referring again to FIG. 5 , intra prediction processing unit 512 may be configured to select an intra prediction mode for a video block to be coded. Intra prediction processing unit 512 may be configured to evaluate a frame and determine an intra prediction mode to use to encode a current block. As described above, possible intra prediction modes may include planar prediction modes, DC prediction modes, and angular prediction modes. Further, it should be noted that in some examples, a prediction mode for a chroma component may be inferred from a prediction mode for a luma prediction mode. Intra prediction processing unit 512 may select an intra prediction mode after performing one or more coding passes. Further, in one example, intra prediction processing unit 512 may select a prediction mode based on a rate-distortion analysis. As illustrated in FIG. 5 , intra prediction processing unit 512 outputs intra prediction data (e.g., syntax elements) to entropy encoding unit 518 and transform coefficient generator 504. As described above, a transform performed on residual data may be mode dependent (e.g., a secondary transform matrix may be determined based on a prediction mode).

Referring again to FIG. 5 , inter prediction processing unit 514 may be configured to perform inter prediction coding for a current video block. Inter prediction processing unit 514 may be configured to receive source video blocks and calculate a motion vector for PUs of a video block. A motion vector may indicate the displacement of a prediction unit of a video block within a current video frame relative to a predictive block within a reference frame. Inter prediction coding may use one or more reference pictures. Further, motion prediction may be uni-predictive (use one motion vector) or bi-predictive (use two motion vectors). Inter prediction processing unit 514 may be configured to select a predictive block by calculating a pixel difference determined by, for example, sum of absolute difference (SAD), sum of square difference (SSD), or other difference metrics. As described above, a motion vector may be determined and specified according to motion vector prediction. Inter prediction processing unit 514 may be configured to perform motion vector prediction, as described above. Inter prediction processing unit 514 may be configured to generate a predictive block using the motion prediction data. For example, inter prediction processing unit 514 may locate a predictive video block within a frame buffer (not shown in FIG. 5 ). It should be noted that inter prediction processing unit 514 may further be configured to apply one or more interpolation filters to a reconstructed residual block to calculate sub-integer pixel values for use in motion estimation. Inter prediction processing unit 514 may output motion prediction data for a calculated motion vector to entropy encoding unit 518.

Referring again to FIG. 5 , filter unit 516 receives reconstructed video blocks and coding parameters and outputs modified reconstructed video data. Filter unit 516 may be configured to perform deblocking and/or Sample Adaptive Offset (SAO) filtering. SAO filtering is a non-linear amplitude mapping that may be used to improve reconstruction by adding an offset to reconstructed video data. It should be noted that as illustrated in FIG. 5 , intra prediction processing unit 512 and inter prediction processing unit 514 may receive modified reconstructed video block via filter unit 216. Entropy encoding unit 518 receives quantized transform coefficients and predictive syntax data (i.e., intra prediction data and motion prediction data). It should be noted that in some examples, coefficient quantization unit 506 may perform a scan of a matrix including quantized transform coefficients before the coefficients are output to entropy encoding unit 518. In other examples, entropy encoding unit 518 may perform a scan. Entropy encoding unit 518 may be configured to perform entropy encoding according to one or more of the techniques described herein. In this manner, video encoder 500 represents an example of a device configured to generate encoded video data according to one or more techniques of this disclosure.

Referring again to FIG. 1 , data encapsulator 107 may receive encoded video data and generate a compliant bitstream, e.g., a sequence of NAL units according to a defined data structure. A device receiving a compliant bitstream can reproduce video data therefrom. Further, as described above, sub-bitstream extraction may refer to a process where a device receiving a ITU-T H.265 compliant bitstream forms a new ITU-T H.265 compliant bitstream by discarding and/or modifying data in the received bitstream. It should be noted that the term conforming bitstream may be used in place of the term compliant bitstream. In one example, data encapsulator 107 may be configured to generate syntax according to one or more techniques described herein. It should be noted that data encapsulator 107 need not necessary be located in the same physical device as video encoder 106. For example, functions described as being performed by video encoder 106 and data encapsulator 107 may be distributed among devices illustrated in FIG. 4 .

As described above, the signaling of DCI information and corresponding profile, tier, level information in JVET-Q2001 is less than ideal. For example, the signaling of syntax element dci_max_sublayers_minus1 is unnecessary. According to the techniques herein syntax element dci_max_sublayers_minus1 may be removed from a DCI. Table 11 illustrates an example of a DCI syntax structure with syntax element dci_max_sublayers_minus1 removed according to the techniques herein. It should be noted that in JVET-Q2001, a VPS allows for signaling a number of output layer sets, specified in one case, by syntax element num_output_layer_sets_minus1 which uses u(8) coding, and for signaling (vps_num_ptls_minus1+1) number of profile-tier-level structures, where vps_num_ptls_minus1 is also u(8) coded. In the example of Table 11, according to the techniques herein, the signaling of syntax element dci_num_ptls_minus1 is coded with u(8) coding. Thus, allowing expressing all possible PTLs (profile, level, tier) in a DCI.

TABLE 11 Descriptor decoding_capability_information_rbsp( ) {  dci_num_ptls_minus1 u(8)  for( i = 0; i <= dci_num_ptls_minus1; i++ )   profile_tier_level( 1, 0 )  dci_extension_flag u(1)  if( dci_extension_flag )   while( more_rbsp_data( ) )    dci_extension_data_flag u(1)  rbsp_trailing_bits( ) }

With respect to Table 11, the semantics of dci_num_ptls_minus1 may be as follows:

-   -   dci_num_ptls_minus1 plus 1 specifies the number of         profile_tier_level( ) syntax structures in the DCI NAL unit. The         value of dci_num_ptls_minus1 shall be in the range of 0 to         vps_num_ptls_minus1, inclusive. It is a requirement of bitstream         conformance that each OLS in a CVS in the bitstream shall         conforms to at least one of the profile_tier_level( ) syntax         structures in the DCI NAL unit.

In another example, the following constraint may be added: The value of dci_num_ptls_minus1 shall be equal to vps_num_ptls_minus1.

Table 12A and Table 12B illustrate examples of a DCI syntax structure with syntax element dci_max_sublayers_minus1 removed according to the techniques herein.

TABLE 12A Descriptor decoding_capability_information_rbsp( ) {  dci_reserved_zero_4bits u(4)  dci_num_ptls_minus1 u(4)  for( i = 0; i <= dci_num_ptls_minus1; i++ )   profile_tier_level( 1, 0 )  dci_extension_flag u(1)  if( dci_extension_flag )   while( more_rbsp_data( ) )    dci_extension_data_flag u(1)  rbsp_trailing_bits( ) }

TABLE 12B Descriptor decoding_capability_information_rbsp( ) {  dci_num_ptls_minus1 u(4)  dci_reserved_zero_4bits u(4)  for( i = 0; i <= dci_num_ptls_minus1; i++ )   profile_tier_level( 1, 0 )  dci_extension_flag u(1)  if( dci_extension_flag )   while( more_rbsp_data( ) )    dci_extension_data_flag u(1)  rbsp_trailing_bits( ) }

With respect to Table 12A and Table 12B, the semantics may be based on the semantics provided above, with in one example, the following semantics for syntax element dci_reserved_zero_4bits.

-   -   dci_reserved_zero_4bits shall be equal to 0 in bitstreams         conforming to this version of this Specification. Other values         for dci_reserved_zero_bit are reserved for future use by ITU-T |         ISO/IEC.

Table 13 illustrates an example of a DCI syntax structure with syntax element dci_max_sublayers_minus1 removed according to the techniques herein.

TABLE 13 Descriptor decoding_capability_information_rbsp( ) {  dci_reserved_zero_bit u(1)  dci_num_ptls_minus1 u(7)  for( i = 0; i <= dci_num_ptls_minus1; i++ )   profile_tier_level( 1, 0 )  dci_extension_flag u(1)  if( dci_extension_flag )   while( more_rbsp_data( ) )    dci_extension_data_flag u(1)  rbsp_trailing_bits( ) }

With respect to Table 13, the semantics may be based on the semantics provided above.

In another example, only some of the bits may available from removing syntax element dci_max_sublayers_minus1 may be used by syntax element dci_num_ptls_minus1. For example, dci_num_ptls_minus1 may use 5 bits and remaining 3 bits included as dci_reserved_zero_3bits. Further, the order of syntax element dci_num_ptls_minus1 and dci reserved zero bit(s) element may be swapped. In another example, an additional syntax element dci_max_layers_minus1 may be signalled in a DCI to specify the maximum number of layers that may be present in each CVS of the bitstream. In one example, 6 bits, i.e., u(6) coding, may be used for the syntax element dci_max_layers_minus1. In one example following may be required: dci_max_layers_minus1 shall be equal to vps_max_layers_minus1.

As described above, WET-Q2001 includes a profile tier level( ) syntax structure. In one example, according to the techniques herein, the syntax elements in profile tier level( ) syntax structure may be rearranged such that syntax element general_level_idc, which is unconditionally signaled, is first syntax element in the structure. Because profileTierPresentFlag can be equal to 0, this allows the unconditionally signaled syntax element general_level_idc to be at a fixed location. Additionally, with this movement of the syntax, all the syntax which is conditionally signaled based on profileTierPresentFlag is together. Thus, requiring only a single if check. Table 14A and Table 14B illustrate an example of a profile_tier_level( ) syntax structure according to the techniques herein. It should be noted that in Table 14B, the position of syntax element general_level_idc is moved to after all the syntax elements which are conditioned on the if(profileTierPresentFlag) condition.

TABLE 14A Descriptor profile_tier_level( profileTierPresentFlag, maxNumSubLayersMinus1 ) {  general_level_idc u(8)  if( profileTierPresentFlag ) {   general_profile_idc u(7)   general_tier_flag u(1)   general_constraint_info( )   num_sub_profiles u(8)   for( i = 0; i < num_sub_profiles; i++ )    general_sub_profile_idc[ i ] u(32)  }  for( i = 0; i < maxNumSubLayersMinus1; i++ )   sublayer_level_present_flag[ i ] u(1)  while( !byte_aligned( ) )   ptl_alignment_zero_bit f(1)  for( i = 0; i < maxNumSubLayersMinus1; i++ )   if( sublayer_level_present_flag[ i ] )    sublayer_level_idc[ i ] u(8) }

TABLE 14B Descriptor profile_tier_level( profileTierPresentFlag, maxNumSubLayersMinus1 ) {  if( profileTierPresentFlag ) {   general_profile_idc u(7)   general_tier_flag u(1)   general_constraint_info( )   num_sub_profiles u(8)   for( i = 0; i < num_sub_profiles; i++ )    general_sub_profile_idc[ i ] u(32)  }  general_level_idc u(8)  for( i = 0; i < maxNumSubLayersMinus1; i++ )   sublayer_level_present_flag[ i ] u(1)  while( !byte_aligned( ) )   ptl_alignment_zero_bit f(1)  for( i = 0; i < maxNumSubLayersMinus1; i++ )   if( sublayer_level_present_flag[ i ] )    sublayer_level_idc[ i ] u(8) }

With respect to Table 14A and Table 14B, the semantics may be based on the semantics provided above. Further, when sps_video_parameter_set_id is equal to 0, the SPS does not refer to a VPS and no VPS is referred to when decoding each CLVS referring to the SPS. In JVET-Q2001, a flag sps_ptl_dpb_hrd_params_present_flag is signaled and controls the presence of the PTL, DPB, HRD parameter structures in an SPS. In JVET-Q2001, when sps_video_parameter_set_id is equal to 0, the PTL, DPB, HRD parameters must be signaled in an SPS. Since these structures are important for video coded, in an improved design, according to the techniques herein, these structures may always be included in a SPS in this case.

In one example, according to the techniques herein, the flag sps_ptl_dpb_hrd_params_present_flag in an SPS may be conditionally signaled only when sps_video_parameter_set_id is not equal to 0 and when not signalled the value of sps_ptl_dpb_hrd_params_present_flag is inferred. When sps_video_parameter_set_id is equal to 0, the SPS does not refer to a VPS and no VPS is referred to when decoding each CLVS referring to the SPS. As a result, various PTL, DPB, HRD parameters need to be signaled in an SPS. Table 15 illustrate the relevant syntax of an SPS when sps_ptl_dpb_hrd_params_present_flag is conditionally signaled according to the techniques herein.

TABLE 15 Descriptor seq_parameter_set_rbsp( ) {  sps_seq_parameter_set_id u(4)  sps_video_parameter_set_id u(4)  sps_max_sublayers_minus1 u(3)  sps_reserved_zero_4bits u(4)  if(sps_video_parameter_set_id ! = 0 )   sps_ptl_dpb_hrd_params_present_flag u(1)  if( sps_ptl_dpb_hrd_params_present_flag )   profile_tier_level( 1, sps_max_sublayers_minus1 )

With respect to Table 15, the semantics may be based on the semantics provided above and the following semantics for sps_ptl_dpb_hrd_params_present_flag:

-   sps_ptl_dpb_hrd_params_present_flag equal to 1 specifies that a     profile_tier_level( ) syntax structure and a dpb_parameters( )     syntax structure are present in the SPS, and a     general_hrd_parameters( ) syntax structure and an     ols_hrd_parameters( ) syntax structure may also be present in the     SPS. sps_ptl_dpb_hrd_params_present_flag equal to 0 specifies that     none of these four syntax structures is present in the SPS. The     value of sps_ptl_dpb_hrd_params_present_flag shall be equal to     vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]]. When not     present sps_ptl_dpb_hrd_params_present_flag is inferred to be equal     to 1.

In this manner, source device 102 represents an example of a device configured to signal a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits, and conditionally signal a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

Referring again to FIG. 1 , interface 108 may include any device configured to receive data generated by data encapsulator 107 and transmit and/or store the data to a communications medium. Interface 108 may include a network interface card, such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can send and/or receive information. Further, interface 108 may include a computer system interface that may enable a file to be stored on a storage device. For example, interface 108 may include a chipset supporting Peripheral Component Interconnect (PCI) and Peripheral Component Interconnect Express (PCIe) bus protocols, proprietary bus protocols, Universal Serial Bus (USB) protocols, I²C, or any other logical and physical structure that may be used to interconnect peer devices.

Referring again to FIG. 1 , destination device 120 includes interface 122, data decapsulator 123, video decoder 124, and display 126. Interface 122 may include any device configured to receive data from a communications medium. Interface 122 may include a network interface card, such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can receive and/or send information. Further, interface 122 may include a computer system interface enabling a compliant video bitstream to be retrieved from a storage device. For example, interface 122 may include a chipset supporting PCI and PCIe bus protocols, proprietary bus protocols, USB protocols, I²C, or any other logical and physical structure that may be used to interconnect peer devices. Data decapsulator 123 may be configured to receive and parse any of the example syntax structures described herein.

Video decoder 124 may include any device configured to receive a bitstream (e.g., a sub-bitstream extraction) and/or acceptable variations thereof and reproduce video data therefrom. Display 126 may include any device configured to display video data. Display 126 may comprise one of a variety of display devices such as a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display. Display 126 may include a High Definition display or an Ultra High Definition display. It should be noted that although in the example illustrated in FIG. 1 , video decoder 124 is described as outputting data to display 126, video decoder 124 may be configured to output video data to various types of devices and/or sub-components thereof. For example, video decoder 124 may be configured to output video data to any communication medium, as described herein.

FIG. 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data according to one or more techniques of this disclosure (e.g., the decoding process for reference-picture list construction described above). In one example, video decoder 600 may be configured to decode transform data and reconstruct residual data from transform coefficients based on decoded transform data. Video decoder 600 may be configured to perform intra prediction decoding and inter prediction decoding and, as such, may be referred to as a hybrid decoder. Video decoder 600 may be configured to parse any combination of the syntax elements described above in Tables 1-15. Video decoder 600 may decode a picture based on or according to the processes described above, and further based on parsed values in Tables 1-15.

In the example illustrated in FIG. 6 , video decoder 600 includes an entropy decoding unit 602, inverse quantization unit 604, inverse transform coefficient processing unit 606, intra prediction processing unit 608, inter prediction processing unit 610, summer 612, post filter unit 614, and reference buffer 616. Video decoder 600 may be configured to decode video data in a manner consistent with a video coding system. It should be noted that although example video decoder 600 is illustrated as having distinct functional blocks, such an illustration is for descriptive purposes and does not limit video decoder 600 and/or sub-components thereof to a particular hardware or software architecture. Functions of video decoder 600 may be realized using any combination of hardware, firmware, and/or software implementations.

As illustrated in FIG. 6 , entropy decoding unit 602 receives an entropy encoded bitstream. Entropy decoding unit 602 may be configured to decode syntax elements and quantized coefficients from the bitstream according to a process reciprocal to an entropy encoding process. Entropy decoding unit 602 may be configured to perform entropy decoding according any of the entropy coding techniques described above. Entropy decoding unit 602 may determine values for syntax elements in an encoded bitstream in a manner consistent with a video coding standard. As illustrated in FIG. 6 , entropy decoding unit 602 may determine a quantization parameter, quantized coefficient values, transform data, and prediction data from a bitstream. In the example, illustrated in FIG. 6 , inverse quantization unit 604 and inverse transform coefficient processing unit 606 receive a quantization parameter, quantized coefficient values, transform data, and prediction data from entropy decoding unit 602 and outputs reconstructed residual data.

Referring again to FIG. 6 , reconstructed residual data may be provided to summer 612. Summer 612 may add reconstructed residual data to a predictive video block and generate reconstructed video data. A predictive video block may be determined according to a predictive video technique (i.e., intra prediction and inter frame prediction). Intra prediction processing unit 608 may be configured to receive intra prediction syntax elements and retrieve a predictive video block from reference buffer 616. Reference buffer 616 may include a memory device configured to store one or more frames of video data. Intra prediction syntax elements may identify an intra prediction mode, such as the intra prediction modes described above. Inter prediction processing unit 608 may receive inter prediction syntax elements and generate motion vectors to identify a prediction block in one or more reference frames stored in reference buffer 616. Inter prediction processing unit 610 may produce motion compensated blocks, possibly performing interpolation based on interpolation filters. Identifiers for interpolation filters to be used for motion estimation with sub-pixel precision may be included in the syntax elements. Inter prediction processing unit 610 may use interpolation filters to calculate interpolated values for sub-integer pixels of a reference block. Post filter unit 614 may be configured to perform filtering on reconstructed video data. For example, post filter unit 614 may be configured to perform deblocking and/or Sample Adaptive Offset (SAO) filtering, e.g., based on parameters specified in a bitstream. Further, it should be noted that in some examples, post filter unit 614 may be configured to perform proprietary discretionary filtering (e.g., visual enhancements, such as, mosquito noise reduction). As illustrated in FIG. 6 , a reconstructed video block may be output by video decoder 600. In this manner, video decoder 600 represents an example of a device configured to parse a syntax element in a decoding capability information syntax structure specifying a number of profile, tier, level syntax structures, wherein the syntax element is 8-bits and conditionally parse a number of profile, tier, level syntax structures in the decoding capability information syntax structure based on the value of the syntax element.

In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.

By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but are instead directed to non-transitory, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.

The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and/or firmware.

Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned embodiments may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

Various examples have been described. These and other examples are within the scope of the following claims. 

What is claimed is:
 1. A device comprising one or more processors configured to: receive a video parameter set raw byte sequence payload syntax structure; parse a first syntax element, providing an identifier for a video parameter set, in the video parameter set raw byte sequence payload syntax structure; parse a first one bit flag syntax element, indicating whether a layer uses an inter-layer prediction, in the video parameter set raw byte sequence payload syntax structure; receive a sequence parameter set raw byte sequence payload syntax structure; parse a second syntax element, providing a value of the first syntax element for the video parameter set, in the sequence parameter set raw byte sequence payload syntax structure; and parse a second one bit flag syntax element in the sequence parameter set raw byte sequence payload syntax structure, wherein the second one bit flag syntax element is only parsed in a case that a value of the second syntax element is not equal to 0, and a value of the second one bit flag syntax element shall have a value of 0 or 1 based on a value of the first one bit flag syntax element.
 2. The device of claim 2, wherein the device includes a video decoder.
 3. A method of decoding video data, the method comprising: receiving a video parameter set raw byte sequence payload syntax structure; parsing a first syntax element, providing an identifier for a video parameter set, in the video parameter set raw byte sequence payload syntax structure; parsing a first one bit flag syntax element, indicating whether a layer uses an inter-layer prediction, in the video parameter set raw byte sequence payload syntax structure; receiving a sequence parameter set raw byte sequence payload syntax structure; parsing a second syntax element, providing a value of the first syntax element for the video parameter set, in the sequence parameter set raw byte sequence payload syntax structure; and parsing a second one bit flag syntax element in the sequence parameter set raw byte sequence payload syntax structure, wherein the second one bit flag syntax element is only parsed in a case that a value of the second syntax element is not equal to 0, and a value of the second one bit flag syntax element shall have a value of 0 or 1 based on a value of the first one bit flag syntax element.
 4. A device comprising one or more processors configured to: signal a video parameter set raw byte sequence payload syntax structure; and signal a sequence parameter set raw byte sequence payload syntax structure; wherein the video parameter set raw byte sequence payload syntax structure includes: (i) a first syntax element providing an identifier for a video parameter set, and (ii) a first one bit flag syntax element indicating whether a layer uses an inter-layer prediction, and the sequence parameter set raw byte sequence payload syntax structure includes: (i) a second syntax element providing a value of the first syntax element for the video parameter set, and (ii) a second one bit flag syntax element, wherein the second one bit flag syntax element is only included in the sequence parameter set raw byte sequence payload syntax structure, in a case that a value of the second syntax element is not equal to 0, and a value of the second one bit flag syntax element shall have a value of 0 or 1 based on a value of the first one bit flag syntax element. 